{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-8084 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-8084 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-8084 is a medium-severity server-side request forgery vulnerability in tigroumeow AI Engine – The Chatbot, AI Framework \u0026 MCP for WordPress, published on 18 Nov 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-8084 and fix it if it is affected.\n\nWhat it is: CVE-2025-8084 is a medium-severity server-side request forgery vulnerability in tigroumeow AI Engine – The Chatbot, AI Framework \u0026 MCP for WordPress, published on 18 Nov 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-8084 in the wild and no public exploit code.\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-8084/ (Markdown: https://insights.sbomify.com/CVE-2025-8084/index.md)","id":"CVE-2025-8084","markdown":"https://insights.sbomify.com/CVE-2025-8084/index.md","name":"CVE-2025-8084","record":{"aliases":["GHSA-2gq9-2c38-4pvg"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress AI plugin","requires_auth":"high_privilege","summary":"Authenticated editors can exploit SSRF in AI Engine to access internal services and retrieve cloud metadata.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"The AI Engine plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 3.1.8 via the rest_helpers_create_images function. This makes it possible for authenticated attackers, with Editor-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services. On Cloud instances, this issue allows for metadata retrieving.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"AI Engine \u003c= 3.1.8 - Authenticated (Editor+) Server-Side Request Forgery","id":"CVE-2025-8084","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Ditty \u003c 3.1.58 - Unauthenticated SSRF","id":"CVE-2025-8085"},"packages":[],"prev":{"headline":"Vuetify Prototype Pollution via Preset options","id":"CVE-2025-8083"},"products":["AI Engine – The Chatbot, AI Framework \u0026 MCP for WordPress"],"published":"2025-11-18","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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["tigroumeow"]},"summary":"Authenticated editors can exploit SSRF in AI Engine to access internal services and retrieve cloud metadata.","url":"https://insights.sbomify.com/CVE-2025-8084/"}