CVE-2026-76053
massUnauthenticated Stored XSS in TranslatePress WordPress Plugin via Comment Injection
TranslatePress – Translate Multilingual sites with AI Translation, a WordPress translation plugin, contains a stored cross-site scripting flaw in all versions up to and including 3.3.3, caused by insufficient input sanitization and output escaping in its HTML parser. An unauthenticated attacker submits a comment containing an anchor tag with href and title attributes alongside a code tag; this structure is permitted by WordPress's comment KSES allowlist, so it is stored verbatim in the database. When the plugin later parses that comment during page translation, the stored markup is injected into the rendered page, causing the attacker's arbitrary web script to execute in the browser of anyone who views the affected page. Any WordPress site running TranslatePress 3.3.3 or earlier that accepts comments is affected, and successful injection could let the attacker hijack sessions or act as viewing users, including administrators (reflected in the CVSS scope change). No exploitation is currently known; EPSS estimates a 0.3% probability of exploitation within 30 days and the issue is not in CISA KEV.
What to do: Update TranslatePress to a version newer than 3.3.3 as soon as the vendor publishes a patched release. Until then, restrict or disable comment submission on translated pages, review stored comments for anchor tags with href/title attributes paired with code tags, and consider WAF rules that block such comment payloads.
| TranslatePress – Translate Multilingual sites with AI Translation (WordPress plugin) | all versions up to and including 3.3.3 |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
The TranslatePress – Translate Multilingual sites with AI Translation plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Noise-Key Injection into HTML Parser in all versions up to, and including, 3.3.3 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. Exploitation is possible because WordPress's comment KSES allowlist permits the payload structure — an anchor tag with href and title attributes alongside a code tag — causing the malicious comment to be stored verbatim in the database, where it is later processed by the vulnerable parser during page translation.
- Ecosystems
- WordPress
- Weakness
- CWE-79
- Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
In the news0 stories
No ingested article mentions this CVE yet.