# CVE-2024-31210: PHP file upload bypass via Plugin installer > Administrators can upload non-zip files as plugins, leading to remote code execution if FTP credentials are required and file editing is disabled. - **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 4 Apr 2024 - **Updated:** 2 Aug 2024 - **Also known as:** BIT-wordpress-2024-31210, BIT-wordpress-multisite-2024-31210, DEBIAN-CVE-2024-31210, GHSA-x79f-xrjv-jx5r, UBUNTU-CVE-2024-31210 ## What is CVE-2024-31210? CVE-2024-31210 is a high-severity vulnerability in Wordpress Wordpress, published on 4 Apr 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link. ### Official 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. Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type) ## Which versions are affected by CVE-2024-31210? 2 open source packages ship an affected version, including wordpress and wordpress-multisite. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `wordpress` | Bitnami | All versions | 4.1.40, 4.2.37, 4.3.33, 4.4.32, 4.5.31, 4.6.28, 4.7.28, 4.8.24, 4.9.25, 5.0.21, 5.1.18, 5.2.20, 5.3.17, 5.4.15, 5.5.14, 5.6.13, 5.7.11, 5.8.9, 5.9.9, 6.0.7, 6.1.5, 6.2.4, 6.3.3, 6.4.3 | | `wordpress-multisite` | Bitnami | All versions | 4.1.40, 4.2.37, 4.3.33, 4.4.32, 4.5.31, 4.6.28, 4.7.28, 4.8.24, 4.9.25, 5.0.21, 5.1.18, 5.2.20, 5.3.17, 5.4.15, 5.5.14, 5.6.13, 5.7.11, 5.8.9, 5.9.9, 6.0.7, 6.1.5, 6.2.4, 6.3.3, 6.4.3 | Products: Wordpress Wordpress. ## How do I fix CVE-2024-31210? Upgrade wordpress to a fixed version for your release line: 4.1.40, 4.2.37, 4.3.33 or 4.4.32. ## Is CVE-2024-31210 being exploited? There is no known exploitation of CVE-2024-31210 in the wild and no public exploit code. ## Other vulnerabilities in Wordpress Wordpress - [CVE-2026-63030](https://insights.sbomify.com/CVE-2026-63030/): WordPress Core Interpretation Conflict (critical 9.8, exploited in the wild) - [CVE-2026-87902](https://insights.sbomify.com/CVE-2026-87902/): WordPress Core Remote File Inclusion (high 8.1, exploited in the wild) - [CVE-2026-60137](https://insights.sbomify.com/CVE-2026-60137/): WordPress Core SQL Injection (medium 5.9, exploited in the wild) - [CVE-2012-2399](https://insights.sbomify.com/CVE-2012-2399/): Cross-site scripting in n/a (critical 10.0) - [CVE-2012-2400](https://insights.sbomify.com/CVE-2012-2400/): Other in n/a (critical 10.0) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-31210 and fix it if it is affected. What it is: CVE-2024-31210 is a high-severity vulnerability in Wordpress Wordpress, published on 4 Apr 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2024-31210 in the wild and no public exploit code. Affected packages and fixed versions: - wordpress (Bitnami): affected all versions; fixed in 4.1.40, 4.2.37, 4.3.33, 4.4.32, 4.5.31, 4.6.28, 4.7.28, 4.8.24, 4.9.25, 5.0.21, 5.1.18, 5.2.20, 5.3.17, 5.4.15, 5.5.14, 5.6.13, 5.7.11, 5.8.9, 5.9.9, 6.0.7, 6.1.5, 6.2.4, 6.3.3, 6.4.3 - wordpress-multisite (Bitnami): affected all versions; fixed in 4.1.40, 4.2.37, 4.3.33, 4.4.32, 4.5.31, 4.6.28, 4.7.28, 4.8.24, 4.9.25, 5.0.21, 5.1.18, 5.2.20, 5.3.17, 5.4.15, 5.5.14, 5.6.13, 5.7.11, 5.8.9, 5.9.9, 6.0.7, 6.1.5, 6.2.4, 6.3.3, 6.4.3 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-31210/ (Markdown: https://insights.sbomify.com/CVE-2024-31210/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-31210 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-31210 - OSV: https://osv.dev/vulnerability/CVE-2024-31210 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-31210/ Summaries are generated and may contain mistakes; the official description above is the record.