EUVD-2026-67397
GHSA-cv4q-6x73-xc63
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconSubmit crafted comment via public form
-
DeliveryWordPress KSES allowlist permits anchor+code payload
-
ExploitMalicious comment stored verbatim in database
-
InstallVictim loads translated page
-
C2TranslatePress parser re-renders comment unescaped
-
ExecuteInjected script executes in victim browser
-
ImpactSession tokens or credentials exfiltrated
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the targeted WordPress site has the TranslatePress plugin installed and active in version 3.3.3 or earlier, and that the plugin's translation rendering is triggered on pages where user-submitted comments appear. The primary limiting condition is WordPress comment submission permissions: if the site allows unauthenticated (guest) comments - which is the WordPress default - no credentials are required to inject the payload. If guest comments are disabled and comment submission requires a registered account, the CVSS PR metric effectively becomes PR:L rather than PR:N, meaningfully reducing mass-exploitation risk. A second limiting condition is that injected payloads only execute when a subsequent user visits a page processed by the TranslatePress translation renderer, introducing an indirect execution dependency. Sites not configured to display comments on translated pages are not exposed to payload execution even if injection is possible. |
| Impact | The CVSS 3.1 base score of 7.2 with vector AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N reflects a high-severity stored XSS with scope change. The PR:N metric is consistent with unauthenticated comment submission (WordPress allows guest comments by default). The UI:N metric scores the injection phase - the attacker does not need victim cooperation to store the payload. However, actual JavaScript execution requires a separate victim page visit, which CVSS 3.1 does not separately model for stored XSS injection vectors. The S:C (scope change) correctly captures cross-context impact: the plugin runs server-side PHP, but the payload executes in the victim's browser context, crossing trust boundaries. No EPSS data was provided in the intelligence package, which limits probabilistic exploitation forecasting. The vulnerability is not in CISA KEV and no POC has been identified, reducing near-term mass-exploitation probability. However, the unauthenticated injection vector and broad plugin deployment make this a realistic target for opportunistic attackers once a PoC is published. Sites with guest comments disabled reduce exposure significantly. |
| Exploit ScenarioDerived | An unauthenticated visitor submits a WordPress comment containing a crafted anchor tag with href and title attributes wrapping a code tag - a structure permitted by the WordPress KSES comment allowlist. The comment is stored verbatim in the database without sanitization. When any subsequent visitor loads a page where TranslatePress's translation renderer processes that comment, the simple_html_dom parser interprets the structure as a translation node and outputs the attacker-controlled payload unescaped into the rendered HTML, executing arbitrary JavaScript in the victim's browser context - enabling session cookie theft, credential harvesting, or malicious redirects. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 28, 2026
Stored Cross-Site Scripting in the TranslatePress WordPress plugin (all versions through 3.3.3) allows unauthenticated attackers to permanently inject arbitrary JavaScript into translated pages visible to all site visitors. The attack exploits a bypass of WordPress's native comment sanitization (KSES): a crafted payload using anchor and code tags is permitted by the allowlist, stored verbatim in the database, and later executed when the plugin's bundled simple_html_dom parser processes comments during page translation rendering. No public exploit code has been identified at time of analysis, and this CVE is not listed in the CISA KEV catalog.
RemediationAI
Upgrade TranslatePress to version 3.3.4 or later immediately; the fix is confirmed via the WordPress Trac changeset at https://plugins.trac.wordpress.org/changeset?old_path=%2Ftranslatepress-multilingual/tags/3.3.3&new_path=%2Ftranslatepress-multilingual/tags/3.3.4. Update via the WordPress admin dashboard under Plugins > Available Updates. As an interim compensating control before patching, disabling public (unauthenticated) comment submission via Settings > Discussion > 'Users must be registered and logged in to comment' removes the unauthenticated injection vector entirely; this is the single most effective workaround with minimal site-function trade-off for sites not dependent on public comment interaction. A Web Application Firewall rule blocking anchor-plus-code tag structures in comment POST bodies can provide additional defense-in-depth but may produce false positives on legitimate markup. Requiring comment moderation (holding all comments for approval) prevents automatic storage of payloads but does not fix the underlying parser flaw and creates operational overhead.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability resides in the plugin's bundled simple_html_dom PHP library (specifically lines L497, L1549, L2125, L2220 of simple_html_dom.php) and its integration with class-translation-render.php (lines L664, L1226), as confirmed by multiple Trac source references. CWE-79 (Improper Neutralization of Input During Web Page Generation) applies at two levels: the plugin fails to sanitize comment content before handing it to the HTML parser, and the translation renderer fails to escape output before writing back to page HTML. The exploit chain exploits a structural gap between WordPress's KSES comment filter - which permits anchor tags with href/title attributes and code tags - and TranslatePress's parser, which treats these allowed structures as translation anchors and re-emits them unescaped. Affected CPE: cpe:2.3:a:cozmoslabs:translatepress_-_translate_multilingual_sites_with_ai_translation:*:*:*:*:*:*:*:* covering all versions up to and including 3.3.3.
Know when Wordpress Plugin gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
PR:N confirmed by unauthenticated comment injection; UI:R reflects that payload execution requires a separate victim page visit, correcting the provided UI:N.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
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.
Executive ViewAI
TranslatePress WordPress plugin through version 3.3.3 contains a stored cross-site scripting vulnerability allowing unauthenticated attackers to permanently inject arbitrary JavaScript into website pages visible to all site visitors. No vendor-released patch is available, placing organizations using this plugin at immediate risk of credential theft, malware distribution, or website defacement affecting end users without direct user interaction.
No vendor-released patch identified at time of analysis. Disable the plugin immediately. For organizations unable to immediately disable: deploy Web Application Firewall rules to block JavaScript and script injection patterns in all user inputs, restrict comment creation to authenticated users, conduct daily database audits of stored comments for anomalous content, and monitor application logs for unexpected client-side script execution.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
Exploit-DB