This is a summary of the AI-generated 10-question deep analysis. The full version (longer answers, follow-up Q&A, related CVEs) requires login. Read the full analysis β
Q1What is this vulnerability? (Essence + Consequences)
π¨ **Essence**: AI Engine plugin exposes Bearer Tokens via REST API `/mcp/v1/`. <br>π₯ **Consequences**: Unauthenticated sensitive data leak β Potential **Privilege Escalation**. Critical integrity & confidentiality loss.
Q2Root Cause? (CWE/Flaw)
π‘οΈ **CWE-200**: Information Exposure. <br>π **Flaw**: The `/mcp/v1/` endpoint leaks Bearer Tokens when the **No-Auth URL** feature is enabled. Poor access control on sensitive API endpoints.
Q3Who is affected? (Versions/Components)
π’ **Vendor**: tigroumeow. <br>π¦ **Product**: AI Engine β The Chatbot, AI Framework & MCP for WordPress. <br>π **Affected**: Versions **3.1.3 and earlier**.
Q4What can hackers do? (Privileges/Data)
π΅οΈ **Hackers Can**: Extract valid Bearer Tokens without login. <br>π **Impact**: Use stolen tokens to impersonate authenticated users. Achieve **Privilege Escalation** and access restricted AI/Chatbot features.
Q5Is exploitation threshold high? (Auth/Config)
β‘ **Threshold**: **LOW**. <br>π **Auth**: None required (Unauthenticated). <br>βοΈ **Config**: Only if **No-Auth URL** is enabled in plugin settings. Easy to trigger via simple HTTP request.
Q6Is there a public Exp? (PoC/Wild Exploitation)
π₯ **Yes, Public**. <br>π **PoC**: Available on GitHub (Nxploited/CVE-2025-11749). <br>π€ **Scanner**: Nuclei templates exist for automated detection. Wild exploitation is highly likely.
Q7How to self-check? (Features/Scanning)
π **Check**: Scan for `/mcp/v1/` endpoint. <br>π‘ **Tool**: Use Nuclei or manual curl requests. <br>π **Verify**: Look for exposed Bearer Token values in the response headers/body when No-Auth is active.
Q8Is it fixed officially? (Patch/Mitigation)
π οΈ **Fix**: Update to version **> 3.1.3**. <br>π **Patch**: Commit 3380753 addresses the issue. Check WordPress plugin repository for the latest secure release.
Q9What if no patch? (Workaround)
π§ **Workaround**: Disable the **No-Auth URL** feature in AI Engine settings. <br>π **Mitigation**: Restrict access to `/mcp/v1/` via .htaccess or WAF rules if patching is delayed.
Q10Is it urgent? (Priority Suggestion)
π΄ **Priority**: **CRITICAL**. <br>β±οΈ **Urgency**: High. CVSS Score indicates High Impact (C:H, I:H, A:H). Immediate patching or mitigation required to prevent token theft and privilege abuse.