WordPress iubenda Plugin Stored XSS in AdSense Regex Rewrite

The iubenda | All-in-one Compliance for GDPR / CCPA Cookie Consent + more plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content via AdSense Regex Rewrite in all versions up to, and including, 3.13.4 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. This vulnerability only manifests when the 'Secondary' parser engine is active (parser_engine=default); it does not exist under the default 'new' DOM-based parser engine.

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 iubenda WordPress plugin versions up to 3.13.4 contain a Stored Cross-Site Scripting (XSS) vulnerability in its AdSense regex rewrite functionality. Due to insufficient input sanitization and output escaping, unauthenticated attackers can inject malicious scripts through comment content that persist in the database and execute whenever any user accesses the affected page. This vulnerability is particularly dangerous because it affects all WordPress sites using this popular GDPR/CCPA compliance plugin, and the attack surface includes any publicly accessible commenting system. Organizations relying on iubenda for compliance management face immediate risk of user session hijacking, credential theft, malware distribution, and reputational damage.

Casky's 323 matching security skills leverage Claude's extended reasoning to detect the attack patterns underlying this vulnerability across MITRE ATT&CK techniques TA0001 (Initial Access) and TA0043 (Reconnaissance). Practitioners using Casky would identify suspicious indicators including: unescaped user-supplied input flowing into HTML contexts within comment processing functions, regex patterns that fail to neutralize script tags or event handlers, and output rendering without proper Content Security Policy enforcement. The platform's skills would flag stored XSS signatures—such as detecting when comment data bypasses sanitization filters and appears in page DOM—and map these findings to the specific attack chain: initial injection via comments, persistence through database storage, and execution during page rendering. Practitioners would see detailed findings highlighting the insufficient use of WordPress escaping functions like `esc_html()` or `wp_kses_post()` in the AdSense rewrite module.

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

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

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

Run the skill that detects this →

X Instagram LinkedIn