WordPress MxChat Plugin Stored DOM XSS via Feedback Parameter

The MxChat – AI Chatbot & Content Generation for WordPress plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'feedback' parameter in all versions up to, and including, 3.2.25 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The stored payload is written by any unauthenticated visitor via a single POST to admin-ajax.php and detonates automatically when any administrator next loads the Transcripts page.

Casky was already ahead

This CVE exploits attack patterns that Casky's 323matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

CVE-2026-110662 is a stored DOM-based cross-site scripting (XSS) vulnerability in the MxChat WordPress plugin that allows unauthenticated attackers to inject malicious scripts through the 'feedback' parameter. Because the plugin fails to properly sanitize input and escape output, any visitor can submit a payload that persists in the application and executes in the browsers of subsequent users who access the affected page. This poses a critical risk to all WordPress installations running vulnerable versions (up to 3.2.25), potentially compromising administrator accounts, stealing session tokens, or redirecting users to phishing sites. The unauthenticated nature of the attack dramatically expands the threat surface, making this vulnerability trivially exploitable at scale.

Casky's 754 security skills mapped to MITRE ATT&CK enable practitioners to detect the attack patterns behind this vulnerability across both initial access (TA0001) and exfiltration (TA0043) techniques. When analyzing WordPress logs and traffic, Casky's Claude AI reasoning identifies suspicious patterns: unusual POST requests to feedback endpoints with HTML/JavaScript payloads, DOM manipulation attempts, and script tag injection in user-controlled fields. Practitioners using Casky would see findings flagging the absence of Content Security Policy headers, missing output encoding in plugin code, and patterns consistent with stored XSS delivery mechanisms. The platform's extended reasoning capabilities correlate these indicators with known exploitation patterns, helping teams prioritize patching efforts and implement compensating controls like WAF rules blocking script injections in feedback parameters before upgrading to patched versions.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

323 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-110662.

Abuse of Public-Facing API: Mobile API Abuse

mobile security · low

Run

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2026-110662

Casky has 323 skills that investigate the attack patterns behind CVE-2026-110662. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn