WordPress TranslatePress Plugin Stored XSS in Comments

The TranslatePress – Translate Multilingual sites with AI Translation plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 3.3.7 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. Exploitation requires the target site to allow unmoderated comment submission on at least one post and to have a secondary language configured — both conditions reflect TranslatePress's primary use case.

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 translation plugin, contains a stored cross-site scripting (XSS) vulnerability in its comment handling functionality. Attackers can inject malicious JavaScript through unmoderated comment submissions, which then executes in the browsers of all users viewing the affected page. This vulnerability affects versions up to 3.3.7 and exploits insufficient input sanitization and output escaping in the 'comment' parameter. WordPress site administrators who permit public comments without strict moderation are at immediate risk, as are their visitors who may unknowingly execute attacker-controlled scripts that could steal credentials, session tokens, or perform actions on their behalf.

Casky's security skills leverage Claude's extended reasoning to correlate this vulnerability pattern across MITRE ATT&CK's Initial Access (TA0001) and Reconnaissance (TA0043) tactics. Practitioners using the platform would observe detection patterns flagging: (1) unsanitized comment submissions reaching template rendering contexts, (2) DOM-based and stored script injection signatures in page source analysis, and (3) suspicious JavaScript payloads in user-submitted content. The 323 matching Casky skills provide contextual alerts on CWE-79 manifestations—such as missing Content Security Policy headers, inadequate HTML entity encoding, or bypass attempts using event handlers and data URIs—enabling security teams to identify compromised pages and trace attack vectors before widespread exploitation occurs.

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

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

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

Run the skill that detects this →

X Instagram LinkedIn