CVE-2026-76053
Received Received - Intake

Stored XSS in TranslatePress WordPress Plugin

Publication date: 2026-08-28

Last updated on: 2026-08-28

Assigner: Wordfence

Description
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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-28
Last Modified
2026-08-28
Generated
2026-09-17
AI Q&A
2026-08-28
EPSS Evaluated
2026-09-15
NVD
CVE-2026-76053
EUVD
EUVD-2026-67397

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
translatepress translate_multilingual_sites_with_ai_translation to 3.3.3 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a Stored Cross-Site Scripting (XSS) vulnerability in the TranslatePress WordPress plugin up to version 3.3.3. It allows unauthenticated attackers to inject malicious scripts into web pages via comment noise-key injection. The issue occurs because the plugin's HTML parser does not properly sanitize input, and WordPress's comment allowlist permits specific HTML tags like anchor and code tags, enabling stored malicious scripts in the database.

Detection Guidance

This vulnerability involves Stored Cross-Site Scripting via Comment Noise-Key Injection in the TranslatePress plugin. Detection requires checking for malicious comments or payloads in WordPress databases or pages. Inspect WordPress comment sections for unusual anchor or code tags with suspicious attributes. Use WordPress admin tools or database queries to review stored comments for payloads like href or title attributes containing script-like content.

Impact Analysis

This vulnerability allows attackers to inject malicious scripts into pages that execute when users visit them. This could lead to theft of user sessions, cookies, or sensitive data, defacement of websites, or redirection to malicious sites. Users with access to the affected site may unknowingly execute these scripts, compromising their data or device security.

Compliance Impact

This vulnerability could lead to data breaches, exposing user data and violating privacy regulations like GDPR and HIPAA. GDPR requires protecting user data and reporting breaches within 72 hours, while HIPAA mandates safeguarding protected health information. A successful exploit may result in non-compliance, legal penalties, and reputational damage.

Mitigation Strategies

Update the TranslatePress plugin to the latest version beyond 3.3.3 to patch the vulnerability. Disable comments on pages where the plugin is active if not required. Review stored comments for suspicious payloads like anchor or code tags.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-76053. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart