The AI Engine – The Chatbot, AI Framework & MCP for WordPress plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.6.5 This is due to missing or incorrect nonce validation on the reauth_for_authorize function. This makes it possible for unauthenticated attackers to create new administrator accounts with attacker-supplied credentials via a CSRF-based REST authentication bypass, granted they can trick a site administrator into performing an action such as clicking on a link. This bypass can be combined with WordPress's ?_method=POST method-override support to convert a top-navigation GET request into an authenticated POST to the REST users endpoint, requiring no existing account on the attacker's part.
CVE-2026-15988
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-01. a secondary CVSS source baseline 8.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(high)
- EG Risk
- 44(Track)EG Risk 44/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 computedSeverity88% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 1, 2026
Last Modified
August 1, 2026
References (7)
- security@wordfencehttps://plugins.trac.wordpress.org/browser/ai-engine/tags/3.6.2/labs/mcp-oauth.php#L120
- security@wordfencehttps://plugins.trac.wordpress.org/browser/ai-engine/tags/3.6.2/labs/mcp-oauth.php#L121
- security@wordfencehttps://plugins.trac.wordpress.org/browser/ai-engine/tags/3.6.2/labs/mcp-oauth.php#L127
- security@wordfencehttps://plugins.trac.wordpress.org/browser/ai-engine/tags/3.6.2/labs/mcp-oauth.php#L49
- security@wordfencehttps://plugins.trac.wordpress.org/changeset/3628188/ai-engine/trunk/labs/mcp-oauth.php
- security@wordfencehttps://plugins.trac.wordpress.org/changeset?old_path=%2Fai-engine/tags/3.6.5&new_path=%2Fai-engine/tags/3.6.6
- security@wordfencehttps://www.wordfence.com/threat-intel/vulnerabilities/id/45816c45-42bc-4163-b700-a1e913f32c97?source=cve
Vendor Advisories for CVE-2026-15988(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 5× in last 7d / 5× 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.
- 2026-08-01 19:32 UTCEG score recompute
- 2026-08-01 19:32 UTCGHSA enrichment
- 2026-08-01 08:25 UTCEG score recompute
- 2026-08-01 07:33 UTCEG score recompute
- 2026-08-01 07:32 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-15988?
When was CVE-2026-15988 disclosed?
What is the CVSS score of CVE-2026-15988?
How do I remediate CVE-2026-15988?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-15988
Is Your Infrastructure Affected by CVE-2026-15988?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.