HomeWordPress vulnerabilitiesTranslatePress
TranslatePress vulnerabilities
TranslatePress has 9 known vulnerabilities in this database. The most recent published record is dated 4 Oct 2026.
- Known vulnerabilities
- 9
- Active installs
- 400,000+
- Latest version
- 3.3.7
- Last updated
- 29 Sep 2026
- Most recent
- 4 Oct 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-103062 | High 7.1 | Up to 3.3.6 | Fixed in a later version (latest 3.3.7) | 3 d ago |
| Cross-site scripting (XSS) CVE-2026-89412 | High 7.2 | Up to 3.3.5 | Fixed in a later version (latest 3.3.7) | 22 Sep 2026 |
| Cross-site scripting (XSS) CVE-2026-76053 | High 7.2 | Up to 3.3.3 | Fixed in a later version (latest 3.3.7) | 28 Aug 2026 |
| Authentication bypass CVE-2026-19632 | Critical 9.8 | Up to 3.3.1 | Fixed in a later version (latest 3.3.7) | 26 Aug 2026 |
| Cross-site scripting (XSS) CVE-2026-18512 | Medium 6.4 | Up to 3.2.6 | Fixed in a later version (latest 3.3.7) | 25 Aug 2026 |
| Cross-site scripting (XSS) CVE-2026-75981 | High 7.2 | Up to 3.2.5 | Fixed in a later version (latest 3.3.7) | 19 Aug 2026 |
| Cross-site scripting (XSS) CVE-2026-18510 | High 7.2 | Up to 3.2.6 | Fixed in a later version (latest 3.3.7) | 6 Aug 2026 |
| Cross-site scripting (XSS) CVE-2026-17505 | Medium 6.1 | Up to 3.2.5 | Fixed in a later version (latest 3.3.7) | 5 Aug 2026 |
| Cross-site scripting (XSS) CVE-2021-24610 | Medium 4.8 | Before 2.0.9 | Fixed in 2.0.9 | 27 Sep 2021 |
Read the published descriptions
- CVE-2026-103062, 4 Oct 2026
- Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Cozmoslabs TranslatePress translatepress-multilingual allows Stored XSS.This issue affects TranslatePress: from n/a through 3.3.6. CVE record
- CVE-2026-89412, 22 Sep 2026
- The TranslatePress - Translate Multilingual sites with AI Translation plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Translation Memory Suggestion Panel (v-html on suggestion.original) in all versions up to, and including, 3.3.5 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. Unauthenticated attackers can seed the translation dictionary's original column with executable HTML because the front-end rendering pipeline decodes entity-encoded payloads via html_entity_decode() before persistence, and the original column is deliberately exempt from kses filtering - meaning no save-time sanitizer neutralizes the stored payload before it is later rendered in an administrator's session. CVE record
- CVE-2026-76053, 28 Aug 2026
- 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. CVE record
- CVE-2026-19632, 26 Aug 2026
- The TranslatePress - Translate Multilingual sites with AI Translation plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.3.1 via the 'trp_get_translations_regular' AJAX action. This makes it possible for unauthenticated attackers to extract the raw administrator password-reset URL - including the plaintext reset key and login parameters stored in the translation dictionary table - enabling full administrator account takeover. This vulnerability is only exploitable when automatic string saving is enabled (the default setting) and the target administrator's profile locale is set to a published secondary language, as these conditions cause the password-reset URL to be persisted as a translatable string in the secondary-language dictionary table. CVE record
- CVE-2026-18512, 25 Aug 2026
- 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. CVE record
- CVE-2026-75981, 19 Aug 2026
- The TranslatePress - Translate Multilingual sites with AI Translation plugin for WordPress is vulnerable to unauthenticated Stored Cross-Site Scripting in versions up to and including 3.2.5. The special gettext markers '#!trpst#' and '#!trpen#' are unconditionally rewritten to '<' and '>' by translate_page() in includes/class-translation-render.php (lines 538-539). Because those markers are plain text with no HTML-special characters, an unauthenticated attacker can embed them in a comment; the markers survive wp_kses, and when the post is viewed in a secondary language the substitution turns the attacker's '#!trpst#img ... #!trpen#' into a real <img> tag. remove_tags_from_output() only strips <script>/<style>, so an <img onerror=...> executes in the visitor's browser. CVE record
- CVE-2026-18510, 6 Aug 2026
- The TranslatePress - Translate Multilingual sites with AI Translation plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content (URL-encoded gettext markers) in all versions up to, and including, 3.2.6 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. Comment moderation may delay exploitation for first-time commenters, but does not prevent it, as the payload uses only WordPress-permitted tags and attributes with percent-encoded characters that pass wp_kses URL validation unmodified. CVE record
- CVE-2026-17505, 5 Aug 2026
- The Translate Multilingual sites - TranslatePress plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 's' parameter in versions up to, and including, 3.2.5. This is due to the translate_page() function unconditionally replacing the plugin's internal #!trpst# and #!trpen# marker tokens with literal angle brackets across the entire HTML page output after WordPress has already sanitized and escaped user input - allowing the attacker to bypass WordPress's normal HTML escaping by using these tokens, which are not HTML special characters, in the search query. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a specially crafted link. CVE record
- CVE-2021-24610, 27 Sep 2021
- The TranslatePress WordPress plugin before 2.0.9 does not implement a proper sanitisation on the translated strings. The 'trp_sanitize_string' function only removes script tag with a regex, still allowing other HTML tags and attributes to execute javascript, which could lead to authenticated Stored Cross-Site Scripting issues. CVE record
What to do if you run TranslatePress
If you run TranslatePress, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new TranslatePress vulnerabilities
Free. We email you when a new vulnerability is published for TranslatePress, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.