CVE-2026-6101

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-07. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

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

The AMP for WP – Accelerated Mobile Pages plugin for WordPress is vulnerable to Arbitrary File Write in versions up to and including 1.1.12. This is due to unsafe ZIP file extraction in the ampforwp_save_local_font() function combined with inadequate cleanup that fails to remove nested directories and files. This makes it possible for authenticated attackers, with Author-level access and above, and permissions granted by an Administrator, to write arbitrary files to the server in a web-accessible location, potentially leading to remote code execution on hosts that execute PHP files in the uploads directory.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
39(Track)
EG Risk 39/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
Severity75% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
46.4%
KEV
Not listed

Published

July 7, 2026

Last Modified

July 7, 2026

References (10)

Vendor Advisories for CVE-2026-6101(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 48× 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-24 14:18 UTCEPSS rescore
  2. 2026-07-24 14:18 UTCEPSS rescore
  3. 2026-07-23 14:18 UTCEPSS rescore
  4. 2026-07-23 14:18 UTCEPSS rescore
  5. 2026-07-23 03:21 UTCEG score recompute
  6. 2026-07-22 14:08 UTCEPSS rescore
  7. 2026-07-22 14:08 UTCEPSS rescore
  8. 2026-07-21 15:25 UTCEPSS rescore
  9. 2026-07-21 15:25 UTCEPSS rescore
  10. 2026-07-20 17:08 UTCEPSS rescore
  11. 2026-07-19 14:31 UTCEPSS rescore
  12. 2026-07-19 02:29 UTCEPSS rescore
  13. 2026-07-18 10:04 UTCEPSS rescore
  14. 2026-07-16 19:32 UTCGHSA enrichment
  15. 2026-07-16 17:03 UTCEPSS rescore
  16. 2026-07-16 07:24 UTCGHSA enrichment
  17. 2026-07-15 19:45 UTCGHSA enrichment
  18. 2026-07-15 16:57 UTCEPSS rescore
  19. 2026-07-15 08:06 UTCGHSA enrichment
  20. 2026-07-15 02:00 UTCEPSS rescore
  21. 2026-07-15 02:00 UTCEPSS rescore
  22. 2026-07-14 20:26 UTCGHSA enrichment
  23. 2026-07-14 08:48 UTCGHSA enrichment
  24. 2026-07-13 22:31 UTCEPSS rescore
  25. 2026-07-13 21:10 UTCGHSA enrichment
Show 23 more
  1. 2026-07-13 09:32 UTCGHSA enrichment
  2. 2026-07-13 06:13 UTCEPSS rescore
  3. 2026-07-13 06:13 UTCEPSS rescore
  4. 2026-07-12 21:54 UTCGHSA enrichment
  5. 2026-07-12 10:16 UTCGHSA enrichment
  6. 2026-07-12 05:46 UTCEPSS rescore
  7. 2026-07-11 22:37 UTCGHSA enrichment
  8. 2026-07-11 10:59 UTCGHSA enrichment
  9. 2026-07-11 08:27 UTCEPSS rescore
  10. 2026-07-11 08:27 UTCEPSS rescore
  11. 2026-07-10 23:21 UTCGHSA enrichment
  12. 2026-07-10 11:43 UTCGHSA enrichment
  13. 2026-07-10 00:05 UTCGHSA enrichment
  14. 2026-07-09 19:10 UTCEPSS rescore
  15. 2026-07-09 19:10 UTCEPSS rescore
  16. 2026-07-09 12:27 UTCGHSA enrichment
  17. 2026-07-09 00:48 UTCGHSA enrichment
  18. 2026-07-08 15:16 UTCEPSS rescore
  19. 2026-07-08 15:16 UTCEPSS rescore
  20. 2026-07-08 13:09 UTCGHSA enrichment
  21. 2026-07-08 01:31 UTCGHSA enrichment
  22. 2026-07-07 13:53 UTCEG score recompute
  23. 2026-07-07 13:53 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-6101?
CVE-2026-6101 is a high vulnerability published on July 7, 2026. The AMP for WP – Accelerated Mobile Pages plugin for WordPress is vulnerable to Arbitrary File Write in versions up to and including 1.1.12. This is due to unsafe ZIP file extraction in the ampforwpsavelocal_font() function combined with inadequate cleanup that fails to remove nested directories…
When was CVE-2026-6101 disclosed?
CVE-2026-6101 was first published in the National Vulnerability Database on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6101 actively exploited?
CVE-2026-6101 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 46.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-6101?
CVE-2026-6101 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-6101?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6101, 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-2026-6101

Explore →

Is Your Infrastructure Affected by CVE-2026-6101?

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

Start Free Scan →Browse All CVEs