WordPress Text-to-Speech Plugin Stored XSS in Comments

The GSpeech TTS – WordPress Text To Speech Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content in all versions up to, and including, 3.22.0 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 mXSS-style transform bypasses WordPress comment kses sanitization because the payload is stored using only kses-allowed tags and attributes; the malicious event handlers and style fragments become active only when the plugin's output-buffer callback rewrites the rendered HTML at request time.

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 GSpeech TTS plugin for WordPress contains a stored cross-site scripting (XSS) vulnerability that allows unauthenticated attackers to inject malicious scripts through comment content. This vulnerability affects all versions up to 3.22.0 and exploits insufficient input sanitization and output escaping, bypassing WordPress's standard comment filtering (kses) through mutation XSS (mXSS) techniques. Any website using this plugin is exposed to attackers who can inject persistent scripts that execute whenever users view affected pages, potentially compromising visitor sessions, stealing credentials, or spreading malware across the WordPress ecosystem.

Casky's 323 mapped security skills leverage Claude's extended reasoning to detect the attack patterns associated with MITRE techniques TA0001 (Initial Access) and TA0043 (Reconnaissance). Practitioners using Casky would identify this vulnerability through detection of unsanitized HTML injection points in comment processing workflows, flagging where user input flows directly to output without proper escaping. The platform's skills map the exploitation chain—from unauthenticated comment submission through stored payload persistence—enabling security teams to trace how attackers bypass WordPress sanitization filters and correlate this with known mXSS transform patterns. Practitioners would see findings highlighting the gap between input validation and output encoding, with specific recommendations to implement content security policies and enforce strict input sanitization ahead of the kses layer.

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

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

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

Run the skill that detects this →

X Instagram LinkedIn