WordPress Plugin Stored XSS via Comment Placeholder Injection

The Transliterator – Multilingual and Multi-script Text Conversion plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content via Predictable {rstr_keep} Placeholder in all versions up to, and including, 2.5.8 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 payload survives WordPress comment save-time sanitization because the tags and attributes used (such as a[title] and code) are permitted by the core comment kses allow-list, and the literal characters comprising the plugin's shortcode markers and placeholder tokens are not stripped.

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 Transliterator – Multilingual and Multi-script Text Conversion WordPress plugin contains a stored cross-site scripting (XSS) vulnerability affecting all versions through 2.5.8. Attackers can inject malicious JavaScript into WordPress comments through a predictable {rstr_keep} placeholder that bypasses input sanitization. Because the payload persists in the database, any user accessing the compromised page triggers the malicious script execution—making this a high-severity threat to WordPress sites relying on this plugin. Unauthenticated attackers can exploit this vulnerability, meaning no special privileges are required to launch an attack.

Casky's 323 matching skills map this vulnerability across MITRE ATT&CK initial access (TA0001) and reconnaissance (TA0043) phases, enabling practitioners to identify both attack delivery and preparation patterns. Using Claude AI's extended reasoning capabilities, practitioners would observe detection signatures flagging insufficient output escaping in comment rendering logic, unsanitized placeholder variables before database storage, and DOM-based script execution patterns in page rendering. The platform helps security teams recognize the attack chain: reconnaissance of plugin versions, crafted comment injection payloads containing script tags within the placeholder syntax, and persistence through WordPress's comment save mechanism. This allows defenders to pinpoint vulnerable plugin instances, audit existing comments for injected payloads, and prioritize remediation before threat actors actively exploit this vulnerability at scale.

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

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

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

Run the skill that detects this →

X Instagram LinkedIn