CVE-2026-12697

MEDIUMPre-NVD 5.45.4—
EchelonGraph scoreHIGH confidence

Score 5.4 from GitHub Security Advisory published 2026-07-31. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this weekElevated
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: Elevated riskExposed: 0

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

The wpForo Forum WordPress plugin before 3.1.2 does not verify that an AI chat conversation belongs to the requesting user before deleting its messages, allowing users with a subscriber-level account to permanently delete the stored AI chat message history of any other user.

CVSS v3
5.4
EG Score
5.4(high)
EG Risk
40(Track)
EG Risk 40/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
Severity54% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

July 31, 2026

Last Modified

July 31, 2026

Advisory Details (1)

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

wpForo Forum < 3.1.2 – Subscriber+ Cross-User AI Chat Message Deletion via IDOR | CVE 2026-12697 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/845362bb-a733-432e-86ac-7bf079d91e0f/

Vendor Advisories for CVE-2026-12697(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 19× in last 7d / 62× 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-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 22:46 UTCGHSA enrichment
  3. 2026-08-19 22:30 UTCEG score recompute
  4. 2026-08-19 22:30 UTCGHSA enrichment
  5. 2026-08-19 17:03 UTCEPSS rescore
  6. 2026-08-18 22:15 UTCEG score recompute
  7. 2026-08-18 22:15 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-17 21:51 UTCEG score recompute
  10. 2026-08-17 21:51 UTCGHSA enrichment
  11. 2026-08-16 21:32 UTCEG score recompute
  12. 2026-08-16 21:32 UTCGHSA enrichment
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-16 02:14 UTCEPSS rescore
  15. 2026-08-15 21:17 UTCEG score recompute
  16. 2026-08-15 21:17 UTCGHSA enrichment
  17. 2026-08-15 01:30 UTCEPSS rescore
  18. 2026-08-14 21:01 UTCEG score recompute
  19. 2026-08-14 21:01 UTCGHSA enrichment
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-13 20:46 UTCGHSA enrichment
  22. 2026-08-12 20:31 UTCEG score recompute
  23. 2026-08-12 20:31 UTCGHSA enrichment
  24. 2026-08-12 13:50 UTCEPSS rescore
  25. 2026-08-11 20:16 UTCEG score recompute
Show 37 more
  1. 2026-08-11 20:16 UTCGHSA enrichment
  2. 2026-08-11 13:42 UTCEPSS rescore
  3. 2026-08-10 23:59 UTCEPSS rescore
  4. 2026-08-10 20:02 UTCGHSA enrichment
  5. 2026-08-09 19:47 UTCEG score recompute
  6. 2026-08-09 19:47 UTCGHSA enrichment
  7. 2026-08-09 13:46 UTCEPSS rescore
  8. 2026-08-08 19:33 UTCEG score recompute
  9. 2026-08-08 19:33 UTCGHSA enrichment
  10. 2026-08-08 16:37 UTCEPSS rescore
  11. 2026-08-07 19:18 UTCEG score recompute
  12. 2026-08-07 19:18 UTCGHSA enrichment
  13. 2026-08-06 19:03 UTCEG score recompute
  14. 2026-08-06 19:03 UTCGHSA enrichment
  15. 2026-08-06 13:46 UTCEPSS rescore
  16. 2026-08-05 19:17 UTCEPSS rescore
  17. 2026-08-05 18:48 UTCGHSA enrichment
  18. 2026-08-04 18:34 UTCEG score recompute
  19. 2026-08-04 18:34 UTCGHSA enrichment
  20. 2026-08-04 15:09 UTCEPSS rescore
  21. 2026-08-03 18:19 UTCEG score recompute
  22. 2026-08-03 18:19 UTCGHSA enrichment
  23. 2026-08-03 10:35 UTCEPSS rescore
  24. 2026-08-02 18:04 UTCEG score recompute
  25. 2026-08-02 18:04 UTCGHSA enrichment
  26. 2026-08-02 02:26 UTCEPSS rescore
  27. 2026-08-01 17:49 UTCEG score recompute
  28. 2026-08-01 17:49 UTCGHSA enrichment
  29. 2026-08-01 04:15 UTCEPSS rescore
  30. 2026-07-31 17:34 UTCEG score recompute
  31. 2026-07-31 17:34 UTCGHSA enrichment
  32. 2026-07-31 17:00 UTCEG score recompute▲ 5.40
  33. 2026-07-31 17:00 UTCGHSA enrichment
  34. 2026-07-31 16:58 UTCMITRE cvelistV5CVSS v3 → 5.4 · severity → MEDIUM
  35. 2026-07-31 07:24 UTCNVD update
  36. 2026-07-31 06:30 UTCEG score recompute
  37. 2026-07-31 06:28 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-12697?
CVE-2026-12697 is a medium vulnerability published on July 31, 2026. The wpForo Forum WordPress plugin before 3.1.2 does not verify that an AI chat conversation belongs to the requesting user before deleting its messages, allowing users with a subscriber-level account to permanently delete the stored AI chat message history of any other user.
When was CVE-2026-12697 disclosed?
CVE-2026-12697 was first published in the National Vulnerability Database on July 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-12697 actively exploited?
CVE-2026-12697 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.3% of all scored CVEs.
What is the CVSS score of CVE-2026-12697?
CVE-2026-12697 has a CVSS v3.1 base score of 5.4 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-12697?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-12697, 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-12697

Explore →

Is Your Infrastructure Affected by CVE-2026-12697?

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

Start Free Scan →Browse All CVEs