CVE-2024-31210

HIGHNVD 7.67.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.6 under NVD CVSS v3. EPSS exploit probability: 1.0% (62nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2024-29110 (ENISA EUVD)Source: ENISA EUVD

7.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.0%CVSS: 7.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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 v3
7.6
EG Score
7.6HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity76% × 45%
Impact severity (EG Severity): CVSS 7.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.0% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
1.0%
EPSS %ILE
62nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.6): severity, escalated by confirmed exploitation. This CVE's 7.6 is its impact severity (EG Severity), not escalated.

EG Severity
7.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
1.0% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 4, 2024

Last Modified

January 7, 2026

Advisory Details (1)

Auto-updated Oct 28, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

PHP file upload bypass via Plugin installer · Advisory · WordPress/wordpress-develop · GitHub

https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-x79f-xrjv-jx5r

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
wordpress5.7.1+dfsg1-2, 5.7.3+dfsg1-0+deb11u1, 5.7.5+dfsg1-0+deb11u1, 5.7.8+dfsg1-0+deb11u1, 5.7.8+dfsg1-0+deb11u2
  • every version up to 5.7.11+dfsg1-0+deb11u1: fixed in 5.7.11+dfsg1-0+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
wordpress6.1.1+dfsg1-1
  • every version up to 6.1.6+dfsg1-0+deb12u1: fixed in 6.1.6+dfsg1-0+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
wordpress—
  • every version up to 6.4.3+dfsg1-1: fixed in 6.4.3+dfsg1-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
wordpress—
  • every version up to 6.4.3+dfsg1-1: fixed in 6.4.3+dfsg1-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 94 of 218 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 6 repeat rows among the latest 100 are merged into the row they repeat. The 124 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:40 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  2. 2026-11-01 16:31 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  3. 2026-10-31 16:30 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  4. 2026-10-30 16:32 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  5. 2026-10-29 16:30 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  6. 2026-10-28 16:29 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  7. 2026-10-28 07:19 UTCEG score recompute
  8. 2026-10-27 16:29 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  9. 2026-10-26 16:29 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  10. 2026-10-25 17:12 UTCEG score recompute
  11. 2026-10-25 16:30 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  12. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  13. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  14. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  15. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  16. 2026-10-20 20:03 UTCEG score recompute
  17. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  18. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  19. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  20. 2026-10-18 07:18 UTCEG score recompute
  21. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  22. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  23. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  24. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  25. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.9% · 60th percentile
Show 69 more
  1. 2026-10-12 17:56 UTCEG score recompute
  2. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  3. 2026-10-11 21:20 UTCEG score recompute
  4. 2026-10-11 16:24 UTCOSV refresh
  5. 2026-10-11 16:14 UTCEG score recompute
  6. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  7. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  8. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  9. 2026-10-08 17:07 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  10. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  11. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  12. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  13. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  14. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  15. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  16. 2026-09-30 19:42 UTCEG score recompute
  17. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  18. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  19. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  20. 2026-09-27 13:43 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  21. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  22. 2026-09-26 00:23 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  23. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  24. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  25. 2026-09-22 14:46 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  26. 2026-09-22 04:15 UTCOSV refresh
  27. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  28. 2026-09-19 15:40 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  29. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  30. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  31. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  32. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  33. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  34. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  35. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  36. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  37. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  38. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  39. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  40. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  41. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  42. 2026-09-03 01:29 UTCOSV refresh
  43. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  44. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  45. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  46. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  47. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  48. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  49. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  50. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  51. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  52. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  53. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  54. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  55. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  56. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  57. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  58. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  59. 2026-08-16 14:00 UTCOSV refresh
  60. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  61. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  62. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  63. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  64. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  65. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  66. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  67. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  68. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  69. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.9% · 57th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2024-31210?
CVE-2024-31210 is a high-severity vulnerability; its CVE record was published on April 4, 2024. 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…
When was the CVE record for CVE-2024-31210 published?
The CVE record for CVE-2024-31210 was published on April 4, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of January 7, 2026; the record at its source may have been updated since.
Is CVE-2024-31210 actively exploited?
CVE-2024-31210 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (62nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-31210?
CVE-2024-31210 has a CVSS v3 base score of 7.6 (NVD).
How do I remediate CVE-2024-31210?
A fix for CVE-2024-31210 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-31210

Explore →

Is Your Infrastructure Affected by CVE-2024-31210?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs