CVE-2024-31210: WordPress is an open publishing platform for the Web.
High CVSS 8.8
- CVE id
- CVE-2024-31210
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| WordPress Runtimes and servers |
< 4.1.40 >= 4.2, < 4.2.37 >= 4.3, < 4.3.33 >= 4.4, < 4.4.32 >= 4.5, < 4.5.31 >= 4.6, < 4.6.28 >= 4.7, < 4.7.28 >= 4.8, < 4.8.24 >= 4.9, < 4.9.25 >= 5.0, < 5.0.21 >= 5.1, < 5.1.18 >= 5.2, < 5.2.20 >= 5.3, < 5.3.17 >= 5.4, < 5.4.15 >= 5.5, < 5.5.14 >= 5.6, < 5.6.13 >= 5.7, < 5.7.11 >= 5.8, < 5.8.9 >= 5.9, < 5.9.9 >= 6.0, < 6.0.7 >= 6.1, < 6.1.5 >= 6.2, < 6.2.4 >= 6.3, < 6.3.3 >= 6.4.0, < 6.4.3 |
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 |
How to fix it
Upgrade WordPress to the fixed release of the line you run: 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.
wp core version
- Update WordPress core to the patched release (Dashboard > Updates, wp core update, or the wordpress image tag).
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
Details
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.
References
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.