CVE-2025-11749

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2025-11-05. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
9.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 75%
  • Public exploit code is available (Metasploit, epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 75%CVSS: 9.8Exploit: Metasploit · epss top5pct · epss high · public exploitExposed: 0

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

The AI Engine plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.1.3 via the /mcp/v1/ REST API endpoint that exposes the 'Bearer Token' value when 'No-Auth URL' is enabled. This makes it possible for unauthenticated attackers to extract the bearer token, which can be used to gain access to a valid session and perform many actions like creating a new administrator account, leading to privilege escalation.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
89(Track)
EG Risk 89/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
Severity98% × 45%
Exploitation75% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
75%
EPSS %ILE
99%
KEV
Not listed

Published

November 5, 2025

Last Modified

April 15, 2026

References (3)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 20× 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-05 19:16 UTCEPSS rescore
  2. 2026-08-04 15:09 UTCEPSS rescore
  3. 2026-08-04 10:37 UTCEPSS rescore
  4. 2026-08-02 02:25 UTCEPSS rescore
  5. 2026-08-01 04:14 UTCEPSS rescore
  6. 2026-07-30 16:26 UTCEPSS rescore
  7. 2026-07-30 01:29 UTCEPSS rescore
  8. 2026-07-26 14:53 UTCEPSS rescore
  9. 2026-07-24 14:16 UTCEPSS rescore
  10. 2026-07-23 02:48 UTCEG score recompute
  11. 2026-07-22 14:07 UTCEPSS rescore
  12. 2026-07-22 14:07 UTCEPSS rescore
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 16:57 UTCEPSS rescore
  15. 2026-07-13 06:12 UTCEPSS rescore
  16. 2026-07-12 05:46 UTCEPSS rescore
  17. 2026-07-12 05:45 UTCEPSS rescore
  18. 2026-07-11 08:26 UTCEPSS rescore
  19. 2026-07-11 08:26 UTCEPSS rescore
  20. 2026-07-08 15:14 UTCEPSS rescore
  21. 2026-07-06 02:22 UTCEPSS rescore
  22. 2026-07-06 02:22 UTCEPSS rescore
  23. 2026-07-04 06:30 UTCEPSS rescore
  24. 2026-07-04 06:30 UTCEPSS rescore
  25. 2026-07-01 15:06 UTCEPSS rescore
Show 58 more
  1. 2026-06-30 23:21 UTCEPSS rescore
  2. 2026-06-28 04:55 UTCEPSS rescore
  3. 2026-06-28 04:55 UTCEPSS rescore
  4. 2026-06-25 13:49 UTCEPSS rescore
  5. 2026-06-25 13:49 UTCEPSS rescore
  6. 2026-06-24 14:04 UTCEPSS rescore
  7. 2026-06-23 21:32 UTCEPSS rescore
  8. 2026-06-23 21:32 UTCEPSS rescore
  9. 2026-06-18 17:52 UTCEPSS rescore
  10. 2026-06-18 17:52 UTCEPSS rescore
  11. 2026-06-17 17:52 UTCEPSS rescore
  12. 2026-06-16 17:52 UTCEPSS rescore
  13. 2026-06-15 17:48 UTCEPSS rescore
  14. 2026-06-15 17:48 UTCEPSS rescore
  15. 2026-06-14 23:17 UTCEPSS rescore
  16. 2026-06-13 22:59 UTCEPSS rescore
  17. 2026-06-12 23:11 UTCEPSS rescore
  18. 2026-06-12 23:11 UTCEPSS rescore
  19. 2026-06-11 13:59 UTCEPSS rescore
  20. 2026-06-10 13:21 UTCEPSS rescore
  21. 2026-06-10 13:21 UTCEPSS rescore
  22. 2026-06-08 14:16 UTCEPSS rescore
  23. 2026-06-08 14:16 UTCEPSS rescore
  24. 2026-06-07 15:24 UTCEPSS rescore
  25. 2026-06-05 22:46 UTCEPSS rescore
  26. 2026-06-05 22:46 UTCEPSS rescore
  27. 2026-06-05 06:10 UTCEPSS rescore
  28. 2026-06-05 06:09 UTCEPSS rescore
  29. 2026-06-04 13:11 UTCEPSS rescore
  30. 2026-06-04 13:11 UTCEPSS rescore
  31. 2026-06-01 13:51 UTCEPSS rescore
  32. 2026-06-01 13:51 UTCEPSS rescore
  33. 2026-05-31 00:16 UTCEPSS rescore
  34. 2026-05-31 00:16 UTCEPSS rescore
  35. 2026-05-28 13:44 UTCEPSS rescore
  36. 2026-05-28 13:44 UTCEPSS rescore
  37. 2026-05-28 13:44 UTCEPSS rescore
  38. 2026-05-27 13:40 UTCEPSS rescore
  39. 2026-05-27 13:40 UTCEPSS rescore
  40. 2026-05-27 13:40 UTCEPSS rescore
  41. 2026-05-26 07:18 UTCEPSS rescore
  42. 2026-05-26 07:18 UTCEPSS rescore
  43. 2026-05-26 07:18 UTCEPSS rescore
  44. 2026-05-26 07:18 UTCEPSS rescore
  45. 2026-05-22 21:16 UTCEPSS rescore
  46. 2026-05-22 21:16 UTCEPSS rescore
  47. 2026-05-22 21:16 UTCEPSS rescore
  48. 2026-05-22 21:16 UTCEPSS rescore
  49. 2026-05-21 22:42 UTCEPSS rescore
  50. 2026-05-21 05:16 UTCEG score recompute
  51. 2026-05-21 05:16 UTCGHSA enrichment
  52. 2026-05-20 22:37 UTCEPSS rescore
  53. 2026-05-20 22:37 UTCEPSS rescore
  54. 2026-05-20 22:37 UTCEPSS rescore
  55. 2026-05-20 22:37 UTCEPSS rescore
  56. 2026-05-20 22:37 UTCEPSS rescore
  57. 2026-05-18 21:30 UTCEPSS rescore
  58. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(3 references)

Working exploit code is in the public domain (1 Metasploit module) (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCNxploited/CVE-2025-11749
    First seen Nov 8, 2025

    AI Engine <= 3.1.3 - Unauthenticated Sensitive Information Exposure to Privilege Escalation

    Open source ↗
  • Metasploitexploit/multi/http/wp_ai_engine_mcp_rce✓ verified
    First seen Nov 4, 2025

    WordPress AI Engine Plugin MCP Unauthenticated Admin Creation to RCE

    Open source ↗
  • Nucleihttp/cves/2025/CVE-2025-11749.yaml
    First seen Jan 1, 2025

    WordPress AI Engine Plugin - Token Exposure

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-11749?
CVE-2025-11749 is a critical vulnerability published on November 5, 2025. The AI Engine plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.1.3 via the /mcp/v1/ REST API endpoint that exposes the 'Bearer Token' value when 'No-Auth URL' is enabled. This makes it possible for unauthenticated attackers to extract the…
When was CVE-2025-11749 disclosed?
CVE-2025-11749 was first published in the National Vulnerability Database on November 5, 2025, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-11749 actively exploited?
CVE-2025-11749 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 75% probability of exploitation in the next 30 days, which ranks it in the top 0.5% of all scored CVEs.
What is the CVSS score of CVE-2025-11749?
CVE-2025-11749 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2025-11749?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-11749, 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-2025-11749

Explore →

Is Your Infrastructure Affected by CVE-2025-11749?

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

Start Free Scan →Browse All CVEs