Advisory

CVE-2026-119167: Cross-site scripting in TranslatePress

CVSS 7.2 (CVE record)Published Nov 8, 2026Last verified Nov 21, 2026

Unauthenticated attackers can inject arbitrary web scripts into pages by exploiting a Stored Cross-Site Scripting vulnerability in the TranslatePress plugin.

Exploited in the wild
Not reported
Installs not updated
At least 12.83%
Affected and fixed versions
ComponentAffectedFixed in
TranslatePress – Translate Multilingual sites with AI Translation (plugin)3.3.8 and earlier3.3.9
Run a free scan of your site

The free scan checks what is visible from outside your site. It does not log in, and it cannot confirm on its own whether this specific issue is present.

Summary

A Stored Cross-Site Scripting (XSS) vulnerability exists in the TranslatePress – Translate Multilingual sites with AI Translation plugin. This vulnerability affects all versions up to and including 3.3.8. A patch is available in version 3.3.9. There is no evidence of active exploitation.

Affected and patched versions

  • TranslatePress – Translate Multilingual sites with AI Translation (plugin translatepress-multilingual): affected 3.3.8 and earlier; fixed in 3.3.9

Is my site vulnerable?

To determine if your site is vulnerable, check the installed version of the TranslatePress – Translate Multilingual sites with AI Translation plugin.

  1. Log in to your WordPress administration dashboard.

  2. Navigate to the "Plugins" menu item, then select "Installed Plugins."

  3. Locate "TranslatePress – Translate Multilingual sites with AI Translation" in the list of installed plugins.

  4. Examine the version number displayed next to the plugin name.

If the installed version is 3.3.8 or earlier, your site is vulnerable to CVE-2026-119167. If your version is 3.3.9 or newer, your site contains the patch for this specific vulnerability.

What an attacker actually does

This vulnerability allows an unauthenticated attacker to inject arbitrary web scripts into pages on a WordPress site running the TranslatePress plugin. The core issue is insufficient input sanitization and output escaping of the 'comment' parameter. This means the plugin does not properly clean or secure user-supplied data before storing it and displaying it on the website.

For a successful attack, two conditions must be met. First, at least one prior comment from the attacker's chosen name and email pair must have been approved. This leverages WordPress's default comment_previously_approved moderation setting. Second, the TranslatePress plugin must have a secondary language configured on the site. If these conditions are in place, the attacker can submit a comment containing malicious script code.

Once the malicious comment is submitted and displayed, the injected scripts will execute in the browser of any user who accesses a page where the malicious content has been injected. This can lead to various unauthorized actions or information disclosure. For example, an attacker could hijack a user's session, redirect users to malicious websites, deface the affected page, or steal sensitive information accessible to the compromised user's browser session. The scripts execute within the context of the user's browser, allowing the attacker to perform actions as if they were the legitimate user.

How to detect a compromise

Detecting a compromise related to a Stored Cross-Site Scripting vulnerability often involves examining the site's database for malicious content and reviewing server logs for suspicious activity. Since this vulnerability involves injecting scripts into comments, the primary focus for detection should be the wp_comments table in your WordPress database.

To check for potential compromise, site administrators should examine the comment_content column within the wp_comments table for unusual content. Specifically, look for HTML script tags (<script>) or other unexpected JavaScript code embedded within comments. Malicious scripts might also be disguised using various encoding techniques or by embedding them within other HTML attributes.

A database query can help identify such entries. Using a tool like phpMyAdmin or a command-line client, an administrator could execute a SQL query similar to the following:

SELECT comment_ID, comment_author, comment_author_email, comment_content
FROM wp_comments
WHERE comment_content LIKE '%<script>%'
OR comment_content LIKE '%javascript:%'
OR comment_content LIKE '%onerror=%'
OR comment_content LIKE '%onmouseover=%';

This query searches for common indicators of XSS payloads within the comment content. Review any results carefully to determine if the content is legitimate or malicious.

Additionally, review server access logs for suspicious activity. Look for multiple comment submissions from the same IP address in a short period, especially if these submissions are followed by attempts to access administrative areas or other sensitive parts of the site. While the initial injection is unauthenticated, successful exploitation of an XSS vulnerability can lead to authenticated actions if an administrator's session is hijacked. Pay attention to any unusual redirects or unexpected modifications to site content that might occur after a user views a page with an injected comment.

How to fix

The vulnerability is addressed in TranslatePress – Translate Multilingual sites with AI Translation version 3.3.9. To fix this issue, update your plugin to the patched version.

Follow these steps to update the TranslatePress plugin:

  1. Backup your site: Before performing any updates, create a complete backup of your WordPress site's files and database. This ensures you can restore your site if any issues arise during the update process.

  2. Access your WordPress dashboard: Log in to your WordPress administration area.

  3. Navigate to Plugins: In the left-hand menu, go to "Plugins" and then click on "Installed Plugins."

  4. Locate TranslatePress: Find "TranslatePress – Translate Multilingual sites with AI Translation" in the list of installed plugins.

  5. Update the plugin: If an update to version 3.3.9 or newer is available, you will see a notification below the plugin name. Click the "Update now" link to initiate the update process.

  6. Verify the update: After the update completes, confirm that the plugin's version number has changed to 3.3.9 or higher.

If for any reason the automatic update fails, you can manually update the plugin:

  1. Download the latest version: Visit the official WordPress plugin directory (wordpress.org/plugins/translatepress-multilingual/) and download the latest version of the TranslatePress plugin to your computer.

  2. Deactivate and delete the old plugin: In your WordPress dashboard, go to "Plugins" -> "Installed Plugins." Deactivate the "TranslatePress – Translate Multilingual sites with AI Translation" plugin, then delete it. This removes the vulnerable files.

  3. Upload the new plugin: Go to "Plugins" -> "Add New" -> "Upload Plugin." Choose the .zip file you downloaded and click "Install Now."

  4. Activate the plugin: Once installed, activate the "TranslatePress – Translate Multilingual sites with AI Translation" plugin.

After updating, consider reviewing your site's comments and database for any previously injected malicious scripts, as the update patches the vulnerability but does not remove existing malicious content.

Timeline

Date

Event

2026-11-06

NVD entry published

2026-11-06

Vulnerability publicly published

2026-11-07

CVE published

Sources

PowerSEC coverage
PowerSEC detects the affected versions on every plan, and has since November 9, 2026. No PowerSEC firewall rule blocks this attack. Update to 3.3.9 or later to remove the vulnerability.
This record contains material that is subject to copyright Copyright 2012-2026 Defiant Inc. Copyright 1999-2026 The MITRE Corporation
Hacked? Talk to us