CVE-2024-31210
WordPress is an open publishing platform for the Web. It's possible fo ...
Overview
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.
Source: OX vulnerability database
Severity
8.8 · HIGH
CVSS 3.1 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Weakness: CWE-434
Affected packages · 2
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| Bitnami | wordpress | <4.1.40>=4.2.0, <4.2.37>=4.3.0, <4.3.33>=4.4.0, <4.4.32>=4.5.0, <4.5.31+19 more | 4.1.404.2.374.3.334.4.324.5.31 |
| Bitnami | wordpress-multisite | <4.1.40>=4.2.0, <4.2.37>=4.3.0, <4.3.33>=4.4.0, <4.4.32>=4.5.0, <4.5.31+19 more | 4.1.404.2.374.3.334.4.324.5.31 |
Open a package to see all its vulnerabilities.
Operating systems · 6 fixes
debian 5 releases · 1 package
| Release | Package | Fixed in |
|---|---|---|
| 10 | wordpress | 5.0.21+dfsg1-0+deb10u1 |
| 11 | wordpress | 5.7.11+dfsg1-0+deb11u1 |
| 12 | wordpress | 6.1.6+dfsg1-0+deb12u1 |
| 13 | wordpress | 6.4.3+dfsg1-1 |
| 14 | wordpress | 6.4.3+dfsg1-1 |
echo 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| wordpress | 6.1.6+dfsg1-0+deb12u1 |
References
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.