{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-12844 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-12844 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-12844 is a high-severity unsafe deserialization vulnerability in tigroumeow AI Engine – The Chatbot, AI Framework \u0026 MCP for WordPress, published on 13 Nov 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-12844 and fix it if it is affected.\n\nWhat it is: CVE-2025-12844 is a high-severity unsafe deserialization vulnerability in tigroumeow AI Engine – The Chatbot, AI Framework \u0026 MCP for WordPress, published on 13 Nov 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-12844 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-12844/ (Markdown: https://insights.sbomify.com/CVE-2025-12844/index.md)","id":"CVE-2025-12844","markdown":"https://insights.sbomify.com/CVE-2025-12844/index.md","name":"CVE-2025-12844","record":{"aliases":["GHSA-qxf4-66fg-4h23"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated attackers can exploit PHP object injection in the AI Engine WordPress plugin to potentially execute code or access data if a POP chain exists.","user_interaction":"required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"The AI Engine plugin for WordPress is vulnerable to PHP Object Injection via PHAR Deserialization in all versions up to, and including, 3.1.8 via deserialization of untrusted input in the 'rest_simpleTranscribeAudio' and 'rest_simpleVisionQuery' functions. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"AI Engine \u003c= 3.1.8 - Authenticated (Subscriber+) PHP Object Injection via PHAR Deserialization","id":"CVE-2025-12844","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2025"},"n_packages":0,"n_references":6,"next":{"headline":"Missing authorization in Tablesome Table – Contact Form DB – WPForms, CF7, Gravity, Forminator, Fluent","id":"CVE-2025-12845"},"packages":[],"prev":{"headline":"Code Injection in Wave Term v0.12.2 allowing TCC Bypass","id":"CVE-2025-12843"},"products":["AI Engine – The Chatbot, AI Framework \u0026 MCP for WordPress"],"published":"2025-11-13","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":"total"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["tigroumeow"]},"summary":"Authenticated attackers can exploit PHP object injection in the AI Engine WordPress plugin to potentially execute code or access data if a POP chain exists.","url":"https://insights.sbomify.com/CVE-2025-12844/"}