CVE-2026-12511

HIGHPre-NVD 8.1Trending — 4 sources updated this week
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 0

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

The AI Engine WordPress plugin before 3.5.5 does not sanitize a user-supplied filename before using it to write a downloaded file, allowing authenticated users with editor-level access to write attacker-controlled bytes to an arbitrary location on the server via path traversal.

CVSS v3
8.1
EG Score
0.0(none)
EPSS
22.3%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 14, 2026

Advisory Details (1)

Auto-updated Jul 14, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

AI Engine < 3.5.5 – Editor+ Arbitrary File Write via Path Traversal | CVE 2026-12511 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/cf3cf59e-da36-429b-8794-5a46587e8462/

Vendor Advisories for CVE-2026-12511(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 6× 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-15 16:57 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-14 13:11 UTCMITRE cvelistV5CVSS v3 → 8.1 · severity → HIGH
  4. 2026-07-14 07:16 UTCNVD update
  5. 2026-07-14 06:05 UTCEG score recompute
  6. 2026-07-14 06:05 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-12511?
CVE-2026-12511 is a high vulnerability published on July 14, 2026. The AI Engine WordPress plugin before 3.5.5 does not sanitize a user-supplied filename before using it to write a downloaded file, allowing authenticated users with editor-level access to write attacker-controlled bytes to an arbitrary location on the server via path traversal.
When was CVE-2026-12511 disclosed?
CVE-2026-12511 was first published in the National Vulnerability Database on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-12511 actively exploited?
CVE-2026-12511 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 22.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-12511?
CVE-2026-12511 has a CVSS v3.1 base score of 8.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 0.0.
How do I remediate CVE-2026-12511?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-12511, 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-12511

Explore →

Is Your Infrastructure Affected by CVE-2026-12511?

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

Start Free Scan →Browse All CVEs