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-9111: CWE-79 Cross-Site Scripting (XSS) in AI ChatBot for WordPress

0
Low
VulnerabilityCVE-2025-9111cvecve-2025-9111cwe-79
Published: Tue Sep 09 2025 (09/09/2025, 06:00:09 UTC)
Source: CVE Database V5
Product: AI ChatBot for WordPress

Description

The AI ChatBot for WordPress WordPress plugin before 7.1.0 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup).

AI-Powered Analysis

AILast updated: 11/13/2025, 21:31:43 UTC

Technical Analysis

CVE-2025-9111 is a stored Cross-Site Scripting (XSS) vulnerability classified under CWE-79, affecting the AI ChatBot for WordPress plugin versions before 7.1.0. The root cause is the plugin's failure to properly sanitize and escape some of its settings data before rendering it in the WordPress admin interface or frontend. This flaw allows high-privilege users, such as administrators, to inject malicious JavaScript code that is persistently stored and executed when other users or administrators view the affected pages. Notably, this vulnerability can be exploited even when the WordPress capability unfiltered_html is disallowed, which is a common security measure in multisite WordPress installations to restrict HTML input. The attack vector requires the attacker to have administrator-level access to the WordPress backend and involves user interaction to trigger the malicious script execution. The CVSS v3.1 base score is 3.5, indicating low severity due to limited confidentiality and integrity impact, no impact on availability, and the requirement for high privileges and user interaction. No public exploits or active exploitation in the wild have been reported to date. The vulnerability was reserved on August 18, 2025, and published on September 9, 2025. The lack of patch links suggests that users should verify plugin updates directly from the vendor or official WordPress plugin repository to ensure they upgrade to version 7.1.0 or later, where this issue is resolved.

Potential Impact

For European organizations, this vulnerability poses a moderate risk primarily to the integrity and confidentiality of data within WordPress sites using the AI ChatBot plugin. Since exploitation requires administrator privileges, the threat is limited to insider threats or attackers who have already compromised admin accounts. Successful exploitation could allow attackers to execute arbitrary JavaScript in the context of the WordPress admin dashboard or frontend, potentially leading to session hijacking, privilege escalation, or defacement. In multisite WordPress environments common in large organizations or managed service providers, the risk is heightened because the unfiltered_html capability is often disabled to enforce content restrictions, yet this vulnerability bypasses that control. The impact on availability is negligible. Organizations relying on WordPress for customer-facing websites, intranets, or e-commerce platforms could face reputational damage and data leakage if this vulnerability is exploited. However, the low CVSS score and absence of known exploits suggest the immediate threat level is low but should not be ignored.

Mitigation Recommendations

European organizations should immediately verify if their WordPress installations use the AI ChatBot plugin and determine the plugin version. If running a version prior to 7.1.0, they should upgrade to the latest available version where this vulnerability is fixed. In the absence of an official patch, organizations can implement temporary mitigations such as restricting administrator access to trusted personnel only and enforcing strong authentication mechanisms like multi-factor authentication (MFA) to reduce the risk of credential compromise. Additionally, administrators should audit plugin settings and sanitize any user-generated content manually if possible. Employing Web Application Firewalls (WAFs) with custom rules to detect and block suspicious script injections in plugin settings can provide an extra layer of defense. Regular security training for administrators to recognize phishing and social engineering attempts can also reduce the risk of privilege escalation. Finally, organizations should monitor WordPress security advisories and update plugins promptly to address emerging vulnerabilities.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
WPScan
Date Reserved
2025-08-18T08:30:27.797Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 68c082c41d20e9585176cdec

Added to database: 9/9/2025, 7:40:52 PM

Last enriched: 11/13/2025, 9:31:43 PM

Last updated: 12/14/2025, 3:34:23 PM

Views: 132

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 enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats