The AI Engine WordPress plugin before 3.5.5 does not verify that a user owns the chatbot conversation referenced by a client-supplied identifier, allowing users with subscriber-level access to read other users' private conversations and take over their conversation records when the discussions feature is enabled.
CVE-2026-12510
Score 5.9 from GitHub Security Advisory published 2026-07-16. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.9; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.9
- EG Score
- 5.9(high)
- EG Risk
- 43(Track)EG Risk 43/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 computedSeverity59% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 4.2%
- KEV
- Not listed
Published
July 16, 2026
Last Modified
July 16, 2026
Advisory Details (1)
Auto-updated Jul 16, 2026AI Engine < 3.5.5 – Subscriber+Chatbot Discussion Disclosure and Takeover via IDOR | CVE 2026-12510 | Plugin Vulnerabilities
https://wpscan.com/vulnerability/b7825c8a-1817-4a17-b641-076e48ac7c2e/Vendor Advisories for CVE-2026-12510(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 8× in last 7d / 15× 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-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:05 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 06:46 UTCEG score recompute▲ 5.90
- 2026-07-17 06:46 UTCGHSA enrichment
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-16 15:53 UTCMITRE cvelistV5CVSS v3 → 5.9 · severity → MEDIUM
- 2026-07-16 08:27 UTCNVD update
- 2026-07-16 06:18 UTCEG score recompute
- 2026-07-16 06:18 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
- CVE-2018-25270EG 9.8CRITICAL
- CVE-2017-20223EG 9.8CRITICAL
- CVE-2019-25487EG 9.8EPSS 94%CRITICAL
- CVE-2019-25235EG 9.8CRITICAL
- CVE-2020-16088EG 9.8CRITICAL
- CVE-2019-15310EG 9.8EPSS 94%CRITICAL
- CVE-2020-11658EG 9.8CRITICAL
- CVE-2019-15913EG 9.8CRITICAL
- CVE-2019-16340EG 9.8EPSS 97%CRITICAL
- CVE-2019-13360EG 9.8EPSS 98%CRITICAL
Frequently asked(5)
What is CVE-2026-12510?
When was CVE-2026-12510 disclosed?
Is CVE-2026-12510 actively exploited?
What is the CVSS score of CVE-2026-12510?
How do I remediate CVE-2026-12510?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-12510
Is Your Infrastructure Affected by CVE-2026-12510?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.