Stored XSS in Meow Lightbox WordPress Plugin

The Meow Lightbox plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'post_content (bbPress reply body)' parameter in all versions up to, and including, 5.6.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 requires the administrator to have enabled Output Buffering, the HtmlDomParser engine, and Aggressive Resolve, as well as a stored-HTML submission surface (such as bbPress anonymous replies) whose kses allow-list preserves img attributes; given these preconditions, a one-shot unauthenticated submission can execute arbitrary JavaScript in the context of any user who views the affected 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-109234 is a Stored Cross-Site Scripting (XSS) vulnerability affecting the Meow Lightbox WordPress plugin through version 5.6.4. The vulnerability exists in the bbPress reply body parameter, where insufficient input sanitization and output escaping allows unauthenticated attackers to inject malicious scripts that persist in the database. When any user accesses an affected page, the injected payload executes in their browser context, potentially leading to session hijacking, credential theft, or malware distribution. This vulnerability impacts WordPress installations using Meow Lightbox with specific configurations enabled (Output Buffering, HtmlDomParser engine, and Aggress mode), making it a critical concern for site administrators and users who interact with compromised content.

Casky's 323 matching skills leverage Claude AI with extended reasoning to detect the attack patterns underlying this vulnerability by mapping to MITRE ATT&CK techniques TA0001 (Initial Access) and TA0043 (Reconnaissance). Practitioners using Casky would identify suspicious patterns such as: abnormal script injection attempts in user-controllable parameters (CWE-79 indicators), stored payloads persisting across page loads, and execution contexts originating from bbPress reply bodies. The platform's skills would surface findings showing how attackers probe for insufficient output escaping, recognize when HTML parsing engines fail to neutralize dangerous content, and detect the conditions where unauthenticated access combined with weak input validation creates exploitable attack chains. Security teams would see detailed breakdowns of how reconnaissance queries targeting plugin configurations correlate with stored XSS injection attempts.

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

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

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

Run the skill that detects this →

X Instagram LinkedIn