CVE-2025-12844 HIGH

CVE-2025-12844: AI Engine <= 3.1.8 - Authenticated (Subscriber+) PHP Object Injection via PHAR Deserialization

Vendor Tigroumeow
Product AI Engine – The Chatbot, AI Framework & MCP for WordPress
Weakness CWE-502 · Unsafe deserialization
Published November 13, 2025
Last update April 8, 2026

CVSS base score

7.1/10
Attack vector Network
Attack complexity High
Privileges required Low
User interaction Required
Confidentiality High
Integrity High

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

The AI Engine plugin for WordPress contains a deserialization vulnerability in versions up to 3.1.8. An authenticated user with low privileges can craft a malicious serialized object that, when deserialized by the plugin, executes arbitrary PHP code on the site. The attacker must trick a site administrator into interacting with a specially crafted link or page. This allows complete compromise of the WordPress installation.

What an attacker can do

03Attacker Capabilities

Run arbitrary PHP code on the site and take full control of WordPress.

Potential impact on your site

04Site Impact

Complete site compromise, data theft, malware injection, and loss of admin control.

Conditions required to exploit

05Prerequisites

Attacker needs a low-privilege WordPress account and must get an admin to click a malicious link.

Key dates

06Disclosure timeline

November 13, 2025 CVE published
April 8, 2026 Record updated