CVE-2026-9109 json
GPTranslate <= 2.31 - Unauthenticated Stored Cross-Site Scripting via REST API Translation Storage
published 2026-06-13 4 mo ago modified 2026-07-23 3 mo ago also EUVD-2026-36642
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 24%
- public exploits
- 0
- none known
Summary
The GPTranslate – Multilingual AI Translation for WordPress: Automatically Translate Websites plugin for WordPress is vulnerable to Stored Cross-Site Scripting via REST API Translation Storage in all versions up to, and including, 2.31 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. The deterministically derived API key (sha256 of the site URL) is printed in the HTML source of every page via the JavaScript variable gptApiKey, meaning any unauthenticated visitor can retrieve the key and submit malicious translation payloads to the /wp-json/gptranslate/v1/request endpoint without any additional precondition.
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 4 mo ago
Exploit prediction
0.32% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N |
Affected products
- john-dagelmore GPTranslate – Multilingual AI Translation for WordPress: Automatically Translate Websites
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/1c93b564-5428-4b0e-bbe8-f1e1e68940ac?source=cve
- plugins.trac.wordpress.org /browser/gptranslate/tags/2.31/assets/js/admin.js#L1
- plugins.trac.wordpress.org /browser/gptranslate/tags/2.31/gptranslate.php#L3654
- plugins.trac.wordpress.org /browser/gptranslate/tags/2.31/gptranslate.php#L3578
- plugins.trac.wordpress.org /browser/gptranslate/tags/2.31/gptranslate.php#L1134
- plugins.trac.wordpress.org /browser/gptranslate/tags/2.27.5/assets/js/admin.js#L1
- plugins.trac.wordpress.org /browser/gptranslate/tags/2.27.5/gptranslate.php#L3654
- plugins.trac.wordpress.org /browser/gptranslate/tags/2.27.5/gptranslate.php#L3578
- plugins.trac.wordpress.org /browser/gptranslate/tags/2.27.5/gptranslate.php#L1134
- plugins.trac.wordpress.org /browser/gptranslate/tags/2.32/assets/js/admin.js#L1
- plugins.trac.wordpress.org /browser/gptranslate/tags/2.32/gptranslate.php#L3574
- plugins.trac.wordpress.org /browser/gptranslate/tags/2.32/gptranslate.php#L1104
Sources
- CVE List CVE-2026-9109
- NVD CVE-2026-9109
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.