Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-5570: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in tigroumeow AI Engine

0
Medium
VulnerabilityCVE-2025-5570cvecve-2025-5570cwe-79
Published: Tue Jul 08 2025 (07/08/2025, 01:43:47 UTC)
Source: CVE Database V5
Vendor/Project: tigroumeow
Product: AI Engine

Description

The AI Engine plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the mwai_chatbot shortcode 'id' parameter in all versions up to, and including, 2.8.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 15:26:38 UTC

Technical Analysis

CVE-2025-5570 is a stored cross-site scripting vulnerability classified under CWE-79 found in the tigroumeow AI Engine plugin for WordPress. The flaw exists in all versions up to and including 2.8.4, specifically in the mwai_chatbot shortcode's 'id' parameter. Due to improper neutralization of input during web page generation, the plugin fails to adequately sanitize and escape user-supplied input. This allows authenticated users with Subscriber-level privileges or higher to inject arbitrary JavaScript code into pages. When other users visit these pages, the malicious scripts execute in their browsers, potentially leading to session hijacking, credential theft, or unauthorized actions performed on behalf of the victim. The vulnerability requires authentication and user interaction (visiting the infected page) but has a low attack complexity and affects the confidentiality and integrity of user data. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N) reflects network attack vector, low complexity, privileges required, user interaction required, scope changed, and low impact on confidentiality and integrity, with no impact on availability. No patches were linked at the time of publication, and no known exploits have been reported in the wild, but the vulnerability poses a credible risk to WordPress sites using this plugin.

Potential Impact

The primary impact of CVE-2025-5570 is the compromise of user confidentiality and integrity on affected WordPress sites. Attackers with minimal privileges can inject persistent malicious scripts, which execute in the browsers of any visitors to the infected pages. This can lead to session hijacking, theft of sensitive information such as cookies or credentials, unauthorized actions performed with victim user privileges, and potential defacement or redirection to malicious sites. The vulnerability does not directly affect availability but can undermine user trust and site reputation. Organizations relying on the tigroumeow AI Engine plugin for AI chatbot functionality face risks of data leakage and unauthorized access, especially if subscriber-level accounts are widely available or compromised. The scope is significant because WordPress is a widely used CMS globally, and this plugin may be deployed on numerous sites, increasing the attack surface. The requirement for authentication limits exploitation somewhat but does not eliminate risk, as subscriber accounts are common and often less monitored.

Mitigation Recommendations

To mitigate CVE-2025-5570, organizations should: 1) Monitor for and apply official patches or updates from tigroumeow promptly once released. 2) Restrict Subscriber-level user permissions to only trusted individuals and review user roles regularly to minimize the number of accounts that can exploit this vulnerability. 3) Implement web application firewall (WAF) rules to detect and block suspicious input patterns targeting the mwai_chatbot shortcode 'id' parameter. 4) Employ additional input validation and output encoding at the application or server level to prevent script injection. 5) Conduct regular security audits and penetration testing focusing on plugin vulnerabilities. 6) Educate site administrators and users about the risks of XSS and encourage cautious behavior when interacting with user-generated content. 7) Consider temporarily disabling or removing the tigroumeow AI Engine plugin if immediate patching is not possible and the risk is unacceptable. 8) Monitor logs for unusual activity indicative of exploitation attempts.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-06-03T20:33:41.338Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 686c84de6f40f0eb72f0003a

Added to database: 7/8/2025, 2:39:26 AM

Last enriched: 2/27/2026, 3:26:38 PM

Last updated: 3/24/2026, 3:06:11 PM

Views: 111

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses