8.8

CVE-2024-31210: wordpress

CVSS: 8.8v3.1HighAnalyzed
AliasesUBUNTU-CVE-2024-31210DEBIAN-CVE-2024-31210
Published 04-04-2024Last modified 02-08-2024
Open JSON

Vulnerability summary

CVE-2024-31210 is a high (CVSS 8.8) vulnerability in wordpress. EPSS estimates a 0.95% chance of exploitation in the next 30 days, higher than 60.4% of scored vulnerabilities.

Overall risk
35/100
0100
Medium · default modelHow is this calculated?
CVSS score
8.8/10
010
High · v3.1 (NVD)
EPSS score
0.95%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 1
DSA-5685-1

Timeline

  1. 04-04-2024
    PublishedVulnerability first disclosed.
  2. 02-08-2024
    Last modifiedVulnerability information updated.

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.

CVSS metrics

4 scores · 4 sources · 1 version

EPSS trend

Probability

0.95%

Chance of exploitation in the next 30 days

Percentile

60%

Versus all other CVEs

30-day change

0.00 pp

From 0.95% on 19-09-2026

19-09-202619-10-2026
EPSS score
0.95%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Wordpress2 products
  • wordpress< 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
  • wordpress-develop≥ 6.4.0, < 6.4.3 | ≥ 6.3.0, < 6.3.3 | ≥ 6.2.0, < 6.2.4 | ≥ 6.1.0, < 6.1.5 | ≥ 6.0.0, < 6.0.7 | ≥ 5.9.0, < 5.9.9 | ≥ 5.8.0, < 5.8.9 | ≥ 5.7.0, < 5.7.11 | ≥ 5.6.0, < 5.6.13 | ≥ 5.5.0, < 5.5.14 | ≥ 5.4.0, < 5.4.15 | ≥ 5.3.0, < 5.3.17 | ≥ 5.2.0, < 5.2.20 | ≥ 5.1.0, < 5.1.18 | ≥ 5.0.0, < 5.0.21 | ≥ 4.9.0, < 4.9.25 | ≥ 4.8.0, < 4.8.24 | ≥ 4.7.0, < 4.7.28 | ≥ 4.6.0, < 4.6.28 | ≥ 4.5.0, < 4.5.31 | ≥ 4.4.0, < 4.4.32 | ≥ 4.3.0, < 4.3.33 | ≥ 4.2.0, < 4.2.37 | < 4.1.40
Debian1 product
  • wordpress< 6.1.6+dfsg1-0+deb12u1 | < 6.4.3+dfsg1-1
Ubuntu1 product
  • wordpressAll versions (No fix recorded)

3 vendors · 4 products

References

5 links