GPTranslate Plugin Stored XSS via Unescaped Translations

The GPTranslate WordPress plugin before 2.34.14 does not properly restrict who can store translations, and does not escape them when outputting them in translated pages, allowing unauthenticated users to perform Stored Cross-Site Scripting attacks when server-side translations are enabled.

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

CVE-2026-103309 is a Stored Cross-Site Scripting (XSS) vulnerability in the GPTranslate WordPress plugin that stems from two critical security failures: insufficient access controls on translation storage and inadequate output encoding. Unauthenticated attackers can inject malicious JavaScript into the translation system, which is then permanently stored and executed in the browsers of all users viewing translated pages. This vulnerability affects any WordPress installation running GPTranslate before version 2.34.14 with server-side translations enabled. The CVSS score of 7.5 reflects the high impact—attackers can steal session tokens, deface content, redirect users, or inject credential-harvesting forms without requiring authentication or user interaction.

Casky's 323 matching skills leverage Claude's extended reasoning to detect the attack patterns mapped to MITRE ATT&CK techniques TA0001 (Initial Access) and TA0043 (Reconnaissance). Practitioners using Casky would identify suspicious patterns including: (1) under TA0001, detection of unauthenticated POST requests to translation endpoints with JavaScript payloads in parameters, indicating exploitation attempts; (2) under TA0043, reconnaissance activity where attackers probe for GPTranslate installations and test translation input fields before launching attacks. The platform's skills would flag anomalies such as translation storage requests from unexpected sources, script tags or event handlers appearing in translation data, and divergent output encoding behavior between authenticated and unauthenticated contexts. Security teams would see findings highlighting the lack of capability validation on translation creation and the absence of Content Security Policy (CSP) headers that could mitigate the stored XSS execution.

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

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

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

Run the skill that detects this →

X Instagram LinkedIn