Skip to main content
Mallory
High

Stored XSS in GPTranslate WordPress Plugin REST API Translation Storage

IdentifiersCVE-2026-9109CWE-79· Improper Neutralization of Input…

CVE-2026-9109 is a stored cross-site scripting vulnerability in the GPTranslate – Multilingual AI Translation for WordPress: Automatically Translate Websites plugin for WordPress affecting all versions up to and including 2.31. The issue is caused by insufficient input sanitization and output escaping in translation data handled through the plugin’s REST API translation storage workflow. An attacker can submit malicious translation payloads to the /wp-json/gptranslate/v1/request endpoint, where the payload is stored and later rendered in site pages. The plugin exposes a deterministically derived API key—described as the SHA-256 of the site URL—in the HTML source of every page via the JavaScript variable gptApiKey. Because any unauthenticated visitor can retrieve this key from page source, the REST endpoint can be abused without authentication or any additional precondition.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an unauthenticated attacker to persist arbitrary JavaScript in translated page content and trigger execution in the browsers of users who visit affected pages. Impact can include session hijacking, credential theft, forced actions in the victim’s browser, defacement, phishing overlays, theft of nonces or other sensitive page data, and potential compromise of administrator accounts if privileged users view the injected content. Because the payload is stored, exploitation can affect multiple visitors over time until the malicious translation content is removed.

Mitigation

If you can’t patch tonight, do this now.

As an interim mitigation, disable the GPTranslate plugin or block access to the vulnerable REST endpoint /wp-json/gptranslate/v1/request at the web server, WAF, or reverse proxy layer if business requirements permit. Monitor translation content and page output for injected scripts, review logs for suspicious requests to the endpoint, and remove malicious stored translations. Restrict exposure of any client-side API key material where possible and apply CSP to reduce XSS impact, though CSP is only a partial mitigation and does not fix the underlying flaw.

Remediation

Patch, then assume compromise.

Update the GPTranslate plugin to a version newer than 2.31 once a vendor fix is available. The fix should ensure strict server-side sanitization and contextual output escaping of translation content, and should remove reliance on a publicly derivable or publicly exposed API key for authorization to the REST endpoint. If no patched version is yet available, disable the vulnerable plugin or the affected translation submission functionality until remediation can be applied.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

ACTIVITY FEED

Recent activity

8 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity8

Community discussion across Reddit, Mastodon, and other social sources.