CVE-2021-29447

HIGHNVD 7.19.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 86% probability of exploitation within the next 30 days (top 0.3% of all CVEs). NVD baseline CVSS 7.1 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Trending — 3 sources updated this weekElevated
7.1
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 86%
CISA-KEV: Not listedEPSS: 86%CVSS: 7.1Exploit: NoneExposed: 0

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

Wordpress is an open source CMS. A user with the ability to upload files (like an Author) can exploit an XML parsing issue in the Media Library leading to XXE attacks. This requires WordPress installation to be using PHP 8. Access to internal files is possible in a successful XXE attack. This has been patched in WordPress version 5.7.1, along with the older affected versions via a minor release. We strongly recommend you keep auto-updates enabled.

CVSS v3
7.1
EG Score
9.0(high)
EG Risk
79(Track)
EG Risk 79/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
Severity90% × 45%
Exploitation86% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.7%
KEV
Not listed

Published

April 15, 2021

Last Modified

November 21, 2024

References (14)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 23× 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 01:59 UTCEG score recompute
  2. 2026-07-22 22:46 UTCEG score recompute
  3. 2026-07-22 14:06 UTCEPSS rescore
  4. 2026-07-22 14:06 UTCEPSS rescore
  5. 2026-07-20 17:05 UTCEPSS rescore
  6. 2026-07-18 22:29 UTCOSV refresh
  7. 2026-07-15 16:55 UTCEPSS rescore
  8. 2026-07-15 16:55 UTCEPSS rescore
  9. 2026-07-13 06:10 UTCEPSS rescore
  10. 2026-07-11 08:25 UTCEPSS rescore
  11. 2026-07-11 08:25 UTCEPSS rescore
  12. 2026-07-07 13:43 UTCEPSS rescore
  13. 2026-07-06 02:21 UTCEPSS rescore
  14. 2026-07-06 02:21 UTCEPSS rescore
  15. 2026-07-05 02:28 UTCEPSS rescore
  16. 2026-07-01 15:03 UTCEPSS rescore
  17. 2026-07-01 05:18 UTCOSV refresh
  18. 2026-06-27 03:06 UTCEPSS rescore
  19. 2026-06-27 03:06 UTCEPSS rescore
  20. 2026-06-24 14:03 UTCEPSS rescore
  21. 2026-06-24 14:03 UTCEPSS rescore
  22. 2026-06-23 21:31 UTCEPSS rescore
  23. 2026-06-23 21:31 UTCEPSS rescore
  24. 2026-06-15 17:46 UTCEPSS rescore
  25. 2026-06-13 22:58 UTCEPSS rescore
Show 23 more
  1. 2026-06-13 22:58 UTCEPSS rescore
  2. 2026-06-13 08:43 UTCOSV refresh
  3. 2026-06-12 23:10 UTCEPSS rescore
  4. 2026-06-10 22:16 UTCEPSS rescore
  5. 2026-06-10 13:20 UTCEPSS rescore
  6. 2026-06-08 14:15 UTCEPSS rescore
  7. 2026-06-07 15:23 UTCEPSS rescore
  8. 2026-06-07 15:23 UTCEPSS rescore
  9. 2026-06-06 13:46 UTCEPSS rescore
  10. 2026-06-06 13:46 UTCEPSS rescore
  11. 2026-06-06 13:46 UTCEPSS rescore
  12. 2026-06-05 22:45 UTCEPSS rescore
  13. 2026-06-05 22:45 UTCEPSS rescore
  14. 2026-06-05 06:09 UTCEPSS rescore
  15. 2026-06-05 06:09 UTCEPSS rescore
  16. 2026-06-04 13:10 UTCEPSS rescore
  17. 2026-06-04 13:10 UTCEPSS rescore
  18. 2026-06-01 13:50 UTCEPSS rescore
  19. 2026-06-01 13:50 UTCEPSS rescore
  20. 2026-05-29 13:42 UTCEPSS rescore
  21. 2026-05-28 13:43 UTCEPSS rescore
  22. 2026-05-28 13:43 UTCEPSS rescore
  23. 2026-05-26 18:12 UTCEG score recompute

Publicly available exploits

(10 references)

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

  • GitHub PoCTea-On/CVE-2021-29447-Authenticated-XXE-WordPress-5.6-5.7
    First seen Jul 4, 2025

    POC to exploit WordPress 5.6-5.7 (PHP 8+) Authenticated XXE Injection.

    Open source ↗
  • GitHub PoC0xRar/CVE-2021-29447-PoC
    First seen Jan 24, 2023

    A proof of concept exploit for a wordpress 5.6 media library vulnerability

    Open source ↗
  • GitHub PoCAbdulazizalsewedy/CVE-2021-29447
    First seen Nov 17, 2022
    Open source ↗
  • GitHub PoCthomas-osgood/CVE-2021-29447
    First seen Nov 15, 2022

    A Golang program to automate the execution of CVE-2021-29447

    Open source ↗
  • GitHub PoCmega8bit/exploit_cve-2021-29447
    First seen Nov 14, 2022
    Open source ↗
  • GitHub PoCM3l0nPan/wordpress-cve-2021-29447
    First seen Nov 11, 2022

    Exploit WordPress Media Library XML External Entity Injection (XXE) to exfiltrate files.

    Open source ↗
  • GitHub PoCelf1337/blind-xxe-controller-CVE-2021-29447
    First seen Nov 6, 2022

    Arbitrary file read controller based on CVE-2021-29447

    Open source ↗
  • Exploit-DBEDB-50304
    First seen Sep 20, 2021

    WordPress 5.7 - 'Media Library' XML External Entity Injection (XXE) (Authenticated)

    Open source ↗
  • GitHub PoCdnr6419/CVE-2021-29447
    First seen Jun 1, 2021

    Wordpress XXE injection 구축 자동화 및 PoC

    Open source ↗
  • GitHub PoCVulnmachines/wordpress_cve-2021-29447
    First seen May 23, 2021

    WordPress XXE vulnerability

    Open source ↗

Frequently asked(5)

What is CVE-2021-29447?
CVE-2021-29447 is a high vulnerability published on April 15, 2021. Wordpress is an open source CMS. A user with the ability to upload files (like an Author) can exploit an XML parsing issue in the Media Library leading to XXE attacks. This requires WordPress installation to be using PHP 8. Access to internal files is possible in a successful XXE attack. This has…
When was CVE-2021-29447 disclosed?
CVE-2021-29447 was first published in the National Vulnerability Database on April 15, 2021, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2021-29447 actively exploited?
CVE-2021-29447 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2021-29447?
CVE-2021-29447 has a CVSS v3 base score of 7.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2021-29447?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2021-29447, 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-2021-29447

Explore →

Is Your Infrastructure Affected by CVE-2021-29447?

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

Start Free Scan →Browse All CVEs