Skip to content
Web

CVE-2026-12511

8.1
High
EPSS 0.29%Patch availableJul 14, 2026

Authenticated path traversal in AI Engine WordPress plugin allows arbitrary file write.

common questions

Is CVE-2026-12511 being exploited?

Not confirmed. CVE-2026-12511 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.29% probability of exploitation in the next 30 days.

How severe is CVE-2026-12511?

CVE-2026-12511 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-12511?

Yes. A fix has been recorded for CVE-2026-12511. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-12511 affect?

CVE-2026-12511 affects AI Engine WordPress plugin < 3.5.5, WordPress sites using AI Engine plugin, Web hosts with writable plugin directories. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-12511?

Update AI Engine plugin to >=3.5.5, audit plugin dirs for unknown files, restrict editor upload rights.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
AI Engine WordPress plugin < 3.5.5WordPress sites using AI Engine pluginWeb hosts with writable plugin directories
impact

Authenticated editor can write attacker-controlled files via path traversal to arbitrary server paths, enabling web shells, remote code execution and site takeover.

action required

Immediate action required

affected versions
Unknown AI Engine
  • affected< 3.5.5

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free