TranslatePress Stored XSS via Gettext Marker Injection

The TranslatePress – Translate Multilingual sites with AI Translation plugin for WordPress is vulnerable to unauthenticated Stored Cross-Site Scripting in versions up to and including 3.2.5. The special gettext markers '#!trpst#' and '#!trpen#' are unconditionally rewritten to '<' and '>' by translate_page() in includes/class-translation-render.php (lines 538-539). Because those markers are plain text with no HTML-special characters, an unauthenticated attacker can embed them in a comment; the markers survive wp_kses, and when the post is viewed in a secondary language the substitution turns the attacker's '#!trpst#img ... #!trpen#' into a real <img> tag. remove_tags_from_output() only strips <script>/<style>, so an <img onerror=...> executes in the visitor's browser.

Casky was already ahead

This CVE exploits attack patterns that Casky's 322matched 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 plugin for multilingual site translation, contains a critical unauthenticated Stored Cross-Site Scripting (XSS) vulnerability in versions up to 3.2.5. The vulnerability stems from improper handling of special gettext markers (#!trpst# and #!trpen#) that are unconditionally converted to HTML angle brackets (< and >) without sanitization. An unauthenticated attacker can inject malicious JavaScript through blog comments or other user-accessible content by embedding these markers alongside script payloads. Once stored, this malicious content executes in the browsers of site administrators and visitors, potentially leading to credential theft, session hijacking, malware distribution, or complete site compromise. With 322 matching security skills across MITRE ATT&CK techniques, any WordPress site using this plugin is exposed to this high-severity threat.

Casky's Claude AI-powered security skills detect this attack pattern by analyzing both Execution techniques (TA0043) and Initial Access vectors (TA0001). Practitioners using Casky would identify suspicious comment submissions containing gettext marker sequences paired with script tags or event handlers, flagging CWE-79 violations during input validation analysis. The platform's extended reasoning capabilities cross-reference stored content against known payload patterns and output encoding failures in the translate_page() function, revealing how attacker-controlled markers bypass the plugin's rewriting logic. Security teams would see findings highlighting: (1) unauthenticated content submission pathways, (2) inadequate output encoding of dynamically generated HTML, and (3) stored payload persistence across page renders—enabling practitioners to prioritize patching and implement Web Application Firewall rules to block requests containing #!trpst# and #!trpen# markers in user-submitted data.

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 →

322 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-75981.

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

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

Run the skill that detects this →

X Instagram LinkedIn