TranslatePress Plugin Stored XSS via Language Parameter

The TranslatePress – Translate Multilingual sites with AI Translation plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment (storage); originals / language / original_language (exfiltration from endpoint)' parameter in all versions up to, and including, 3.3.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.

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

TranslatePress, a popular WordPress multilingual translation plugin, contains a critical stored cross-site scripting (XSS) vulnerability affecting all versions up to 3.3.8. The flaw exists in the language parameter handling within the comment storage and original language endpoints, where insufficient input sanitization allows unauthenticated attackers to inject malicious JavaScript. When users access pages containing the injected payload, the stored script executes in their browsers with full context, potentially compromising session tokens, stealing credentials, or redirecting users to malicious sites. With an estimated 100,000+ active installations, this vulnerability poses significant risk to WordPress sites serving multilingual audiences, as attackers need no authentication to exploit it.

Casky's 323 matched skills leverage Claude's extended reasoning to detect the attack patterns underlying this vulnerability across MITRE ATT&CK techniques TA0001 (Reconnaissance) and TA0043 (Reconnaissance). Practitioners using Casky would identify detection signatures for: (1) suspicious parameter payloads in comment endpoints containing script tags or event handlers, (2) stored XSS pattern analysis showing script persistence across page requests, and (3) outbound data exfiltration attempts from the language/original_language endpoint that indicate successful payload execution. Security teams would see findings highlighting improper input validation, missing output encoding, and the attack chain from initial injection through post-exploitation data theft—enabling them to prioritize patching, implement WAF rules, and audit for existing malicious comments before threat actors leverage this actively exploitable 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-120537.

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

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

Run the skill that detects this →

X Instagram LinkedIn