CVE-2025-12844 is a deserialization vulnerability classified under CWE-502 affecting the tigroumeow AI Engine plugin for WordPress. The vulnerability arises from unsafe deserialization of untrusted input in two REST API functions: 'rest_simpleTranscribeAudio' and 'rest_simpleVisionQuery'. These functions accept serialized PHP objects via PHAR deserialization, allowing an attacker with at least Subscriber-level authentication to inject malicious PHP objects. The core risk stems from PHP Object Injection, which can lead to arbitrary code execution, file deletion, or data disclosure if a suitable POP (Property Oriented Programming) gadget chain exists in the WordPress environment. The plugin itself does not contain a POP chain, so exploitation depends on the presence of other vulnerable plugins or themes that provide such chains. The attack vector is network-based (remote), but requires low privilege authentication and user interaction (triggering the REST API). The CVSS 3.1 score of 7.1 reflects high confidentiality, integrity, and availability impacts but with higher attack complexity due to the prerequisite conditions. No patches are currently linked, and no active exploits have been reported. This vulnerability highlights the risks of insecure deserialization in PHP applications, especially in extensible platforms like WordPress where multiple plugins/themes interact.

For European organizations, this vulnerability poses a significant risk to WordPress sites running the tigroumeow AI Engine plugin, particularly those with multiple plugins or themes installed that may contain POP chains. Successful exploitation could lead to remote code execution, allowing attackers to compromise website integrity, steal sensitive data, or disrupt availability by deleting files. This could result in data breaches, defacement, or service outages, impacting brand reputation and compliance with GDPR and other data protection regulations. Organizations in sectors with high reliance on WordPress for public-facing or internal applications—such as media, education, government, and SMEs—are especially vulnerable. The requirement for authenticated access somewhat limits exposure but does not eliminate risk, as Subscriber-level accounts are common and often easier to obtain via phishing or credential stuffing. The lack of known exploits in the wild provides a window for proactive mitigation, but the potential impact remains high if exploited.

1. Immediately update the tigroumeow AI Engine plugin to a patched version once available. Monitor vendor announcements for patch releases. 2. In the interim, restrict access to the vulnerable REST API endpoints ('rest_simpleTranscribeAudio' and 'rest_simpleVisionQuery') by implementing Web Application Firewall (WAF) rules or disabling these endpoints if not required. 3. Audit all installed plugins and themes for known POP chains or unsafe deserialization patterns to reduce the risk of chained exploitation. 4. Enforce strict user role management and monitor for suspicious Subscriber-level account activity to prevent unauthorized access. 5. Employ PHP configuration hardening, such as disabling PHAR deserialization if feasible, or using PHP security extensions that detect or block unsafe deserialization. 6. Regularly back up WordPress sites and test restoration procedures to mitigate impact from potential destructive attacks. 7. Conduct security scans and penetration tests focusing on deserialization vulnerabilities and REST API abuse. 8. Educate administrators and developers about the risks of insecure deserialization and the importance of secure coding practices in plugin development.