MCB WordPress Plugin Stored XSS via Request Headers

The MCB WordPress plugin through 1.0.0 does not sanitise or escape request header values before storing them and later rendering them in the administrator statistics grid, allowing unauthenticated attackers to store malicious JavaScript that executes in an administrator's browser session when the statistics page is viewed.

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

The MCB WordPress plugin through version 1.0.0 contains a stored cross-site scripting (XSS) vulnerability in its administrator statistics grid. The plugin fails to sanitize or escape HTTP request header values before persisting them to storage and rendering them in the admin dashboard. This allows unauthenticated attackers to inject malicious JavaScript by crafting requests with poisoned headers—the payload remains stored until an administrator views the statistics page, where the script executes in the admin's authenticated browser session. WordPress sites running this plugin are immediately at risk, as the vulnerability requires no authentication to exploit and directly targets privileged administrator accounts, making it a high-severity threat (CVSS 8.8) for any installation with this plugin active.

Casky's 323 matching skills leverage Claude AI's extended reasoning to detect the attack patterns behind this vulnerability across the MITRE ATT&CK framework. The platform maps this threat to TA0001 (Initial Access) and TA0043 (Reconnaissance), identifying both the injection vector and the privilege escalation opportunity. Practitioners using Casky would observe detection signals around CWE-79 input validation failures—specifically flagged patterns where request headers are logged without sanitization, stored in databases without encoding, and rendered in admin interfaces without output escaping. The findings would highlight the attack chain: reconnaissance of plugin versions, crafting malicious headers to trigger the vulnerability, and persistence through stored payloads that activate when administrators access statistics. Security teams would see actionable recommendations for input sanitization, output encoding, and Content Security Policy deployment, directly tied to MITRE techniques used in real-world WordPress plugin exploitation.

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-110525.

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-110525

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

Run the skill that detects this →

X Instagram LinkedIn