{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11749 exists.","fix":"No fix has been published for CVE-2025-11749 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-11749 is a critical vulnerability in tigroumeow AI Engine – The Chatbot, AI Framework \u0026 MCP for WordPress, published on 5 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-11749 and fix it if it is affected.\n\nWhat it is: CVE-2025-11749 is a critical vulnerability in tigroumeow AI Engine – The Chatbot, AI Framework \u0026 MCP for WordPress, published on 5 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11749 exists.\n\nAffected product: tigroumeow AI Engine – The Chatbot, AI Framework \u0026 MCP for WordPress. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-11749/ (Markdown: https://insights.sbomify.com/CVE-2025-11749/index.md)","id":"CVE-2025-11749","markdown":"https://insights.sbomify.com/CVE-2025-11749/index.md","name":"CVE-2025-11749","record":{"aliases":["GHSA-q6x7-qqgq-h832"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress AI plugin","requires_auth":"none","summary":"Unauthenticated attackers can extract bearer tokens via a REST API endpoint when No-Auth URL is enabled, leading to privilege escalation.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-11-04","github_poc":1,"max_poc_stars":9,"metasploit":1,"nuclei":1,"refs":[{"date":"2025-11-08T03:19:59Z","kind":"github_poc","ref":"https://github.com/Nxploited/CVE-2025-11749","stars":9,"title":"AI Engine \u003c= 3.1.3 - Unauthenticated Sensitive Information Exposure to Privilege Escalation"},{"date":"2025-11-04","kind":"metasploit","ref":"exploit/multi/http/wp_ai_engine_mcp_rce","stars":null,"title":"WordPress AI Engine Plugin MCP Unauthenticated Admin Creation to RCE"},{"date":null,"kind":"nuclei","ref":"http/cves/2025/CVE-2025-11749.yaml","stars":null,"title":"WordPress AI Engine Plugin - Token Exposure"}],"tier":"weaponised"},"has_fix":null,"headline":"AI Engine \u003c= 3.1.3 - Unauthenticated Sensitive Information Exposure to Privilege Escalation","id":"CVE-2025-11749","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"User Enumeration via Distinct Error Messages in langgenius/dify-web","id":"CVE-2025-11750"},"packages":[],"prev":{"headline":"Groups \u003c= 3.7.0 - Authenticated (Subscriber+) Insecure Direct Object Reference to Arbitrary Group Join","id":"CVE-2025-11748"},"products":["AI Engine – The Chatbot, AI Framework \u0026 MCP for WordPress"],"published":"2025-11-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["tigroumeow"]},"summary":"Unauthenticated attackers can extract bearer tokens via a REST API endpoint when No-Auth URL is enabled, leading to privilege escalation.","url":"https://insights.sbomify.com/CVE-2025-11749/"}