TranslatePress <= 3.2.6 - Authenticated (Subscriber+) Stored Cross-Site Scripting via Approved Comment Body in Translation Editor
Strategic Overview
- Status
- Patched in 3.3
- Affected Version
<= 3.2.6- CVSS
- 6.4Medium
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2026-18512
At a glance
CVE-2026-18512 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the TranslatePress WordPress plugin, affecting versions <= 3.2.6. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.3; sites on affected versions should update now. Disclosed August 2026, reported by momopon1415.
Vulnerability Overview
The TranslatePress – Translate Multilingual sites with AI Translation plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Approved Comment Body Rendered in Translation Editor Strings Dropdown in all versions up to, and including, 3.2.6 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Reaching this weakness in TranslatePress <= 3.2.6 takes an account at Subscriber level or above. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For TranslatePress the fix is 3.3: builds <= 3.2.6 are affected, anything from 3.3 onward is not.
Remediation
Update to version 3.3, or a newer patched version
How does WordSec protect against this?
An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: TranslatePress 3.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in TranslatePress – Translate Multilingual sites with AI Translation
- 8.1CVE-2025-58592: TranslatePress <= 2.10.2 PHP Object Injection
CVE-2025-58592 - 7.2CVE-2025-30773: TranslatePress <= 2.9.6 PHP Object Injection
CVE-2025-30773 - 7.2CVE-2022-3141: TranslatePress <= 2.3.2 SQL Injection
CVE-2022-3141 - 4.8CVE-2021-24610: TranslatePress <= 2.0.8 Stored Cross-Site Scripting
CVE-2021-24610 - 4.3CVE-2024-34827: Translate Multilingual sites – TranslatePress CSRF
CVE-2024-34827
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C