CVE-2024-31210

What it is

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.

At a glance

Exploitability

Can be exploited over the network with an admin-level account, but needs a user to act. High risk of data exposure, data tampering, service disruption.

Exploit odds

1.0% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2024-04-04 23:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 07:27 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.0% in the next 30 days (EPSS).
• Severity: 7.6 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2024-04-04 23:15 UTC

Last modified

2026-06-17 07:27 UTC

Exploit probability

1.0% · EPSS, next 30 days

Weakness

CWE-434 · Unrestricted file upload

Record status

Analyzed

Affected

• WordPress < 4.1.40
• WordPress < 4.2.37
• WordPress < 4.3.33
• WordPress < 4.4.32
• WordPress < 4.5.31
• WordPress < 4.6.28
• WordPress < 4.7.28
• WordPress < 4.8.24

Attack profile CVSS 3.1 · 7.6

Attack vector

Network

Complexity

High

Privileges needed

High

User interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2024-31210.md and follow it. Check whether this project is affected by CVE-2024-31210. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge