CMB2 Plugin Stored XSS via Unescaped Textarea Fields

The CMB2 plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the '<textarea_code field id> (e.g. kl_code, kl_post_code)' parameter in all versions up to, and including, 2.13.1 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 front-end save path requires only a CMB2 box nonce, which is emitted to all visitors including unauthenticated guests via a simple GET request, making the attack trivially reachable without any credentials on sites that expose a public CMB2 form writing a textarea_code field.

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

CMB2 is a popular WordPress metabox plugin used by thousands of sites to create custom fields and data structures. This vulnerability allows unauthenticated attackers to inject malicious JavaScript into textarea code fields (like kl_code or kl_post_code) that persists in the database as stored XSS. When any user visits a page containing the injected field, the malicious script executes in their browser with their privileges—potentially stealing session tokens, credentials, or redirecting users to phishing sites. The critical issue is that the front-end save functionality only requires a CMB2 nonce (a token sent to all page visitors), making exploitation trivial for attackers who can craft requests without authentication. Any WordPress site running CMB2 up to version 2.13.1 is affected, and the vulnerability is particularly dangerous because it affects content visible to all users, not just administrators.

Casky's 323 matching skills detect this attack pattern by mapping to MITRE techniques TA0001 (Initial Access) and TA0043 (Reconnaissance). The platform's Claude-powered analysis would identify the stored XSS signature through detection of: (1) unsanitized input flowing into textarea parameters without proper HTML entity encoding, (2) nonce validation failures or overly permissive nonce scope, and (3) lack of output escaping on field rendering. Practitioners reviewing findings would see the attack chain progression—reconnaissance phase where attackers enumerate CMB2 field names, followed by initial access through unauthenticated POST requests exploiting the weak nonce validation. The extended reasoning capability would highlight that this is a data exfiltration and persistence vector, flagging the specific textarea field parameters as injection points and recommending immediate patching to 2.13.2+ or later, plus implementation of Content Security Policy headers to limit XSS impact.

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

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

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

Run the skill that detects this →

X Instagram LinkedIn