CVE-2026-12041: Stored XSS in Chatra Live Chat Plugin ≤1.0.12 for WordPress
The Chatra Live Chat plugin for WordPress contains a security flaw that allows administrators to inadvertently inject malicious scripts into the site through the plugin's settings panel. When an administrator (or anyone with equivalent permissions) saves settings in the plugin, those settings are not properly validated or cleaned, meaning an attacker with admin access could craft a malicious payload that runs in visitors' browsers. This risk is limited to WordPress multisite networks or sites where the 'unfiltered_html' capability has been restricted—standard single-site WordPress installations with unfiltered_html enabled are not affected.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 4.4 MEDIUM · CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N
- Weaknesses (CWE)
- CWE-79
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-07-08 / 2026-07-08
NVD description (verbatim)
The Chatra Live Chat + ChatBot + Cart Saver plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 1.0.12 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.
3 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-12041 is a Stored Cross-Site Scripting (XSS) vulnerability in the Chatra Live Chat + ChatBot + Cart Saver plugin affecting all versions through 1.0.12. The vulnerability stems from insufficient input sanitization and output escaping in the admin settings interface. An authenticated attacker with administrator-level or higher privileges can inject arbitrary JavaScript into the WordPress database via the plugin's settings form. The injected script persists and executes in the context of any user who visits an affected page, provided the installation is either a WordPress multisite deployment or a single-site instance with the unfiltered_html capability disabled. The CVSS v3.1 base score is 4.4 (Medium), reflecting the requirement for high-privilege authentication and specific configuration constraints.
Business impact
A compromised administrator account or insider threat could use this vulnerability to inject malicious scripts that steal user data, capture credentials, redirect visitors to phishing pages, or perform unauthorized actions on behalf of visitors. For organizations running multisite WordPress networks, a single compromised admin account could potentially affect multiple sites simultaneously. The impact is contained to stored XSS rather than site-wide compromise—an attacker cannot directly access the server or escalate privileges—but the ability to manipulate page content poses reputational and compliance risks, particularly for sites handling sensitive visitor data.
Affected systems
The Chatra Live Chat + ChatBot + Cart Saver plugin in versions up to and including 1.0.12 is affected. Vulnerability only manifests in WordPress multisite installations or single-site installations where the unfiltered_html user capability has been disabled (a common hardening measure). Standard WordPress single-site installations where administrators have the unfiltered_html capability enabled are not affected, as WordPress's core editor will sanitize the content before storage.
Exploitability
Exploitation requires authentication as an administrator or higher-privileged user and is not remotely exploitable by unauthenticated attackers. The attacker must have direct access to the WordPress admin panel and knowledge of the plugin's settings interface. The vulnerability does not appear on the CISA Known Exploited Vulnerabilities (KEV) catalog, indicating no active exploitation in the wild has been publicly reported. However, the barrier to exploitation is relatively low for any attacker who has already compromised or been granted administrative credentials.
Remediation
Update the Chatra Live Chat + ChatBot + Cart Saver plugin to a version newer than 1.0.12 that includes input sanitization and output escaping fixes. Verify the patched version against the official Chatra plugin repository or vendor advisory. Until patching is possible, restrict administrative access to trusted personnel only and monitor admin activity logs for suspicious plugin setting changes. Additionally, ensure unfiltered_html capability is appropriately scoped in your WordPress user roles.
Patch guidance
Check the official WordPress Plugin Directory or Chatra's support channels for a patched version of the plugin released after 1.0.12. Apply the update to all WordPress installations running the affected plugin, prioritizing multisite networks and single-site instances with unfiltered_html disabled. After updating, verify that the plugin's admin settings no longer accept or render raw HTML or JavaScript input. Test in a staging environment first to ensure compatibility with your site configuration and other installed plugins.
Detection guidance
Monitor WordPress admin audit logs and database activity for changes to the Chatra plugin settings. Search the WordPress wp_options or wp_postmeta tables for suspicious script tags (e.g., <script>, javascript:, onerror=) in plugin configuration values if you suspect compromise. Use WordPress security plugins with admin activity logging and integrity monitoring to flag unauthorized changes to plugin settings. Review stored XSS patterns in web application firewall (WAF) logs if available. Inspect the page source of public-facing pages for unexpected inline script tags or event handlers that do not appear in your site's legitimate templates.
Why prioritize this
While the CVSS score of 4.4 places this in the Medium severity tier, prioritization should consider your specific WordPress architecture and administrative access controls. Multisite network operators should treat this with higher urgency given the potential for cross-site impact. Single-site installations with unfiltered_html enabled face minimal risk. The requirement for admin-level authentication significantly limits real-world exposure compared to unauthenticated vulnerabilities, but the persistence of stored XSS makes this a business continuity concern if your admin tier has been compromised or contains unvetted users.
Risk score, explained
The CVSS v3.1 score of 4.4 reflects a Medium severity vulnerability because it requires high-privilege authentication (PR:H), has complex attack conditions (AC:H due to specific WordPress configurations), and delivers limited impact scope (CWE-79 XSS typically does not directly compromise confidentiality, integrity, or availability at the system level). The attack is confined to the web application context and does not grant remote code execution or server-level access. However, the changed scope (S:C in the vector) indicates potential impact across security boundaries in a multisite context, which partially offsets the low authentication barrier within that scope.
Frequently asked questions
Does this vulnerability affect my WordPress site if I'm running a standard single-site installation with default settings?
Most likely not. The vulnerability only manifests in WordPress multisite networks or single-site installations where the unfiltered_html user capability has been explicitly disabled (typically a security hardening measure). If you're running a standard WordPress single-site with default WordPress user roles and capabilities, the unfiltered_html capability is enabled for administrators by default, and WordPress's sanitization will prevent the attack.
If I update the plugin, do I need to clean up any existing malicious scripts that may have been injected?
Yes. Updating the plugin stops new injections but does not automatically remove previously stored malicious content. After patching, audit your site's page and post content, particularly the Chatra plugin settings and any pages using Chatra widgets. If you suspect compromise, search the database for suspicious script tags or review page source code for unexpected inline scripts. Consider temporarily disabling the plugin and removing suspicious content, then re-enabling the patched version.
Can an unauthenticated user exploit this vulnerability?
No. This vulnerability requires the attacker to have authenticated administrator-level access to the WordPress admin panel. Unauthenticated visitors cannot directly exploit it. However, if your administrator account or a high-privilege user account has been compromised through phishing, weak passwords, or another security incident, an attacker could then use that access to inject malicious scripts.
Is this vulnerability being actively exploited?
There is no public evidence of active exploitation. The vulnerability does not appear on CISA's Known Exploited Vulnerabilities (KEV) catalog, which tracks vulnerabilities with confirmed active exploitation. However, the absence of public reports does not guarantee no exploitation; prioritize patching especially if your organization's admin accounts are exposed or if you operate a multisite network.
This analysis is provided for informational purposes and reflects publicly available vulnerability data as of the published date. CVSS scores and vulnerability classifications are subject to interpretation and may change as additional context emerges. Organizations should verify patch availability and compatibility with their specific WordPress environment before applying updates. This assessment does not constitute a substitute for thorough security review by qualified personnel or vendor advisories. No exploit code or weaponized proof-of-concept is provided or endorsed. Always test patches in a non-production environment first. SEC.co does not provide legal advice; consult your legal and compliance teams regarding disclosure obligations and incident response procedures. Source: NVD (public-domain), retrieved 2026-08-16. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2016-20070MEDIUMPrivilege Escalation & Stored XSS in WordPress Booking Calendar Contact Form 1.0.23
- CVE-2018-25384MEDIUMStored XSS in Wikidforum 2.20 Allows Authenticated Attackers to Inject Malicious Scripts
- CVE-2019-25731MEDIUMStored XSS in Zuz Music 2.1 Contact Form
- CVE-2019-25737MEDIUMStored XSS in Live Chat Unlimited 2.8.3 – Admin Session Compromise
- CVE-2019-25739MEDIUMGigToDo 1.3 Stored XSS Vulnerability in Proposal Descriptions
- CVE-2019-25742MEDIUMStored XSS in Zoner Real Estate WordPress Theme 4.1.1 – Admin Account Compromise Risk
- CVE-2019-25743MEDIUMWordPress Soliloquy Lite 2.5.6 Stored XSS Vulnerability
- CVE-2019-25744MEDIUMWordPress Popup Builder 3.49 Stored XSS Vulnerability – Exploit Prevention & Patch Guide