CVE-2024-4439

HIGHNVD 7.28.5▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.5 because EPSS predicts 71% probability of exploitation within the next 30 days (top 0.7% of all CVEs). NVD baseline CVSS 7.2 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
7.2
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 71%
CISA-KEV: Not listedEPSS: 71%CVSS: 7.2Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

WordPress Core is vulnerable to Stored Cross-Site Scripting via user display names in the Avatar block in various versions up to 6.5.2 due to insufficient output escaping on the display name. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. In addition, it also makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that have the comment block present and display the comment author's avatar.

CVSS v3
7.2
EG Score
8.5(high)
EG Risk
82(Track)
EG Risk 82/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity85% × 45%
Exploitation71% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.3%
KEV
Not listed

Published

May 3, 2024

Last Modified

January 5, 2026

References (10)

Weakness Classification(1)

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

Data Freshness Timeline

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

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-23 02:40 UTCEG score recompute▼ 0.50
  2. 2026-07-22 14:07 UTCEPSS rescore
  3. 2026-07-22 14:07 UTCEPSS rescore
  4. 2026-07-20 17:06 UTCEPSS rescore
  5. 2026-07-19 14:30 UTCEPSS rescore
  6. 2026-07-19 14:30 UTCEPSS rescore
  7. 2026-07-19 02:28 UTCEPSS rescore
  8. 2026-07-19 02:28 UTCEPSS rescore
  9. 2026-07-15 16:57 UTCEPSS rescore
  10. 2026-07-15 16:56 UTCEPSS rescore
  11. 2026-07-14 11:40 UTCOSV refresh
  12. 2026-07-13 22:29 UTCEPSS rescore
  13. 2026-07-12 05:45 UTCEPSS rescore
  14. 2026-07-12 05:45 UTCEPSS rescore
  15. 2026-07-09 19:09 UTCEPSS rescore
  16. 2026-07-09 19:09 UTCEPSS rescore
  17. 2026-07-04 06:30 UTCEPSS rescore
  18. 2026-07-01 15:05 UTCEPSS rescore
  19. 2026-06-28 14:07 UTCEPSS rescore
  20. 2026-06-27 03:07 UTCEPSS rescore
  21. 2026-06-27 03:07 UTCEPSS rescore
  22. 2026-06-26 12:09 UTCOSV refresh
  23. 2026-06-25 13:49 UTCEPSS rescore
  24. 2026-06-24 14:04 UTCEPSS rescore
  25. 2026-06-24 14:04 UTCEPSS rescore
Show 33 more
  1. 2026-06-23 21:32 UTCEPSS rescore
  2. 2026-06-23 21:32 UTCEPSS rescore
  3. 2026-06-21 14:56 UTCEPSS rescore
  4. 2026-06-21 01:59 UTCEPSS rescore
  5. 2026-06-21 01:58 UTCEPSS rescore
  6. 2026-06-18 17:52 UTCEPSS rescore
  7. 2026-06-18 17:52 UTCEPSS rescore
  8. 2026-06-17 17:52 UTCEPSS rescore
  9. 2026-06-17 17:52 UTCEPSS rescore
  10. 2026-06-16 17:52 UTCEPSS rescore
  11. 2026-06-16 17:52 UTCEPSS rescore
  12. 2026-06-15 17:47 UTCEPSS rescore
  13. 2026-06-13 22:59 UTCEPSS rescore
  14. 2026-06-13 22:59 UTCEPSS rescore
  15. 2026-06-13 22:59 UTCEPSS rescore
  16. 2026-06-12 23:11 UTCEPSS rescore
  17. 2026-06-12 23:11 UTCEPSS rescore
  18. 2026-06-10 22:18 UTCEPSS rescore
  19. 2026-06-08 19:11 UTCOSV refresh
  20. 2026-06-06 13:46 UTCEPSS rescore
  21. 2026-06-06 13:46 UTCEPSS rescore
  22. 2026-06-05 22:46 UTCEPSS rescore
  23. 2026-06-05 22:46 UTCEPSS rescore
  24. 2026-06-05 06:09 UTCEPSS rescore
  25. 2026-06-05 06:09 UTCEPSS rescore
  26. 2026-06-02 20:12 UTCEPSS rescore
  27. 2026-05-28 13:44 UTCEPSS rescore
  28. 2026-05-28 13:44 UTCEPSS rescore
  29. 2026-05-28 13:44 UTCEPSS rescore
  30. 2026-05-26 13:43 UTCEPSS rescore
  31. 2026-05-26 13:43 UTCEPSS rescore
  32. 2026-05-24 02:58 UTCEG score recompute
  33. 2026-05-24 02:58 UTCGHSA enrichment

Publicly available exploits

(3 references)

Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCd0rb/CVE-2024-4439
    First seen May 6, 2024

    The provided exploit code leverages a stored Cross-Site Scripting (XSS) vulnerability (CVE-2024-4439) in WordPress Core versions up to 6.5.1.

    Open source ↗
  • GitHub PoCMielPopsssssss/CVE-2024-4439
    First seen May 6, 2024

    CVE-2024-4439 PoC

    Open source ↗
  • Nucleihttp/cves/2024/CVE-2024-4439.yaml
    First seen Jan 1, 2024

    WordPress Core <6.5.2 - Cross-Site Scripting

    Open source ↗

Frequently asked(5)

What is CVE-2024-4439?
CVE-2024-4439 is a high vulnerability published on May 3, 2024. WordPress Core is vulnerable to Stored Cross-Site Scripting via user display names in the Avatar block in various versions up to 6.5.2 due to insufficient output escaping on the display name. This makes it possible for authenticated attackers, with contributor-level access and above, to inject…
When was CVE-2024-4439 disclosed?
CVE-2024-4439 was first published in the National Vulnerability Database on May 3, 2024, with the most recent update on January 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-4439 actively exploited?
CVE-2024-4439 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-4439?
CVE-2024-4439 has a CVSS v3 base score of 7.2 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.5.
How do I remediate CVE-2024-4439?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-4439, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-4439

Explore →

Is Your Infrastructure Affected by CVE-2024-4439?

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

Start Free Scan →Browse All CVEs