Skip to content
Fencer Vulns
high 7.7

CVE-2024-31210 json

PHP file upload bypass via Plugin installer

published 2024-04-03 2 y ago modified 2026-09-08 2 mo ago also BIT-wordpress-2024-31210 , BIT-wordpress-multisite-2024-31210 , EUVD-2024-29110 , GHSA-x79f-xrjv-jx5r

cvss
7.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 62%
public exploits
0
none known

Summary

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.

Patch / fix

  • bitnami wordpress 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
  • bitnami wordpress-multisite 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 wordpress-develop 6.4.3
  • wordpress Debian 12 6.1.6+dfsg1-0+deb12u1
  • wordpress Debian 14, Debian 13 6.4.3+dfsg1-1

debian advisories DEBIAN-CVE-2024-31210

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2 y ago

Exploit prediction

1.00% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.7 CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
OSV 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected 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
>=4.6.0, <4.6.28
>=4.7.0, <4.7.28
>=4.8.0, <4.8.24
>=4.9.0, <4.9.25
>=5.0.0, <5.0.21
>=5.1.0, <5.1.18
>=5.2.0, <5.2.20
>=5.3.0, <5.3.17
>=5.4.0, <5.4.15
>=5.5.0, <5.5.14
>=5.6.0, <5.6.13
>=5.7.0, <5.7.11
>=5.8.0, <5.8.9
>=5.9.0, <5.9.9
>=6.0.0, <6.0.7
>=6.1.0, <6.1.5
>=6.2.0, <6.2.4
>=6.3.0, <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
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
>=4.6.0, <4.6.28
>=4.7.0, <4.7.28
>=4.8.0, <4.8.24
>=4.9.0, <4.9.25
>=5.0.0, <5.0.21
>=5.1.0, <5.1.18
>=5.2.0, <5.2.20
>=5.3.0, <5.3.17
>=5.4.0, <5.4.15
>=5.5.0, <5.5.14
>=5.6.0, <5.6.13
>=5.7.0, <5.7.11
>=5.8.0, <5.8.9
>=5.9.0, <5.9.9
>=6.0.0, <6.0.7
>=6.1.0, <6.1.5
>=6.2.0, <6.2.4
>=6.3.0, <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

Affected products

  • WordPress wordpress-develop

Classification

Weakness
  • CWE-434 Unrestricted Upload of File with Dangerous Type
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of WordPress/wordpress-develop published their own advisory on GitHub. Reviewed sources take precedence over it.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.