Plugins · translatepress-multilingual · data as of 2026-11-01
Is TranslatePress safe? Known vulnerabilities and latest version
- Latest version
- 3.3.8
- Last updated
- 2026-10-13
- Active installs
- 400,000+
- Known issues on record
- 14
- Unpatched in latest
- 0
- Tested up to WP
- 7.1.4 · PHP 7.4+
Translate your site visually, directly from the front-end. Go multilingual in minutes using automatic AI translation. Works with any theme or plugin. — by Cozmoslabs
What to do
- Update to the latest version (3.3.8). Anything older than 3.3.8 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get translatepress-multilingual --field=version shows what you run; wp plugin update translatepress-multilingual updates it.
Check your version
Known vulnerabilities
14 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
high 7.2 CVE-2026-107768 · published 2026-10-16
Stored cross-site scripting (XSS) in TranslatePress (3.3.7 and older)
- Affected
- 3.3.7 and older
- Fixed in
- 3.3.8 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The TranslatePress – Translate Multilingual sites with AI Translation plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 3.3.7 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 requires the target site to allow unmoderated comment submission on at least one post and to have a secondary language configured — both conditions reflect TranslatePress's primary use case.
NVD CVE-2026-107768Wordfence advisoryCode change (fix)Plugin source
high 7.1 CVE-2026-103062 · published 2026-10-04
Stored cross-site scripting (XSS) in TranslatePress (3.3.6 and older)
- Affected
- 3.3.6 and older
- Fixed in
- 3.3.7
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
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.
high 7.2 CVE-2026-89412 · published 2026-09-22
Stored cross-site scripting (XSS) in TranslatePress (3.3.5 and older)
- Affected
- 3.3.5 and older
- Fixed in
- 3.3.6 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
NVD CVE-2026-89412Wordfence advisoryCode change (fix)Plugin source
high 7.2 CVE-2026-76053 · published 2026-08-28
Stored cross-site scripting (XSS) in TranslatePress (3.3.3 and older)
- Affected
- 3.3.3 and older
- Fixed in
- 3.3.4 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
NVD CVE-2026-76053Wordfence advisoryCode change (fix)Plugin source
critical 9.8 CVE-2026-19632 · published 2026-08-26
Information disclosure in TranslatePress (3.3.1 and older)
- Affected
- 3.3.1 and older
- Fixed in
- 3.3.2 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
NVD CVE-2026-19632Wordfence advisoryCode change (fix)Plugin source
medium 6.4 CVE-2026-18512 · published 2026-08-25
Stored cross-site scripting (XSS) in TranslatePress (3.2.6 and older)
- Affected
- 3.2.6 and older
- Fixed in
- 3.3 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
NVD CVE-2026-18512Wordfence advisoryCode change (fix)Plugin source
critical 9.8 CVE-2026-78267 · published 2026-08-24
Privilege escalation in TranslatePress (3.3.2 and older)
- Affected
- 3.3.2 and older
- Fixed in
- 3.3.3
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Unauthenticated Privilege Escalation in TranslatePress <= 3.3.2 versions.
high 7.1 CVE-2026-66582 · published 2026-08-20
Cross-site scripting (XSS) in TranslatePress (3.3.2 and older)
- Affected
- 3.3.2 and older
- Fixed in
- 3.3.3
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Unauthenticated Cross Site Scripting (XSS) in TranslatePress <= 3.3.2 versions.
high 7.2 CVE-2026-75981 · published 2026-08-19
Stored cross-site scripting (XSS) in TranslatePress (3.2.5 and older)
- Affected
- 3.2.5 and older
- Fixed in
- 3.2.6 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
high 7.2 CVE-2026-18510 · published 2026-08-06
Stored cross-site scripting (XSS) in TranslatePress (3.2.6 and older)
- Affected
- 3.2.6 and older
- Fixed in
- 3.3 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
NVD CVE-2026-18510Wordfence advisoryCode change (fix)Plugin source
medium 6.1 CVE-2026-17505 · published 2026-08-05
Reflected cross-site scripting (XSS) in TranslatePress (3.2.5 and older)
- Affected
- 3.2.5 and older
- Fixed in
- 3.2.6 *
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
NVD CVE-2026-17505Wordfence advisoryCode change (fix)Plugin source
high 8.1 CVE-2025-58592 · published 2025-11-06
PHP object injection in TranslatePress (2.10.2 and older)
- Affected
- 2.10.2 and older
- Fixed in
- 2.10.3
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Deserialization of Untrusted Data vulnerability in Cozmoslabs TranslatePress translatepress-multilingual allows Object Injection.This issue affects TranslatePress: from n/a through <= 2.10.2.
high 7.2 CVE-2025-30773 · published 2025-03-27
PHP object injection in TranslatePress (2.9.6 and older)
- Affected
- 2.9.6 and older
- Fixed in
- 2.9.7
- Access needed (per CVSS)
- Needs an admin-level account
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Deserialization of Untrusted Data vulnerability in Cozmoslabs TranslatePress translatepress-multilingual allows Object Injection.This issue affects TranslatePress: from n/a through <= 2.9.6.
medium 4.3 CVE-2024-34827 · published 2024-05-14
Cross-site request forgery (CSRF) in TranslatePress (2.7.5 and older)
- Affected
- 2.7.5 and older
- Fixed in
- 2.7.6
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Cross-Site Request Forgery (CSRF) vulnerability in Cozmoslabs, Razvan Mocanu, Madalin Ungureanu, Cristophor Hurduban TranslatePress.This issue affects TranslatePress: from n/a through 2.7.5.
Recent activity
- 2026-10-13 — latest release on wordpress.org (3.3.8).
- 2026-10-16 — Stored cross-site scripting (XSS) disclosed (CVE-2026-107768), fixed in 3.3.8.
- 2026-10-04 — Stored cross-site scripting (XSS) disclosed (CVE-2026-103062), fixed in 3.3.7.
- 2026-09-22 — Stored cross-site scripting (XSS) disclosed (CVE-2026-89412), fixed in 3.3.6.
Get an email when TranslatePress has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for TranslatePress (translatepress-multilingual) is published or a fix ships. Unsubscribe in one click.
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/translatepress-multilingual (Plugins API), fetched 2026-11-01.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-01. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/translatepress-multilingual"><img src="https://laskyr.com/plugins/translatepress-multilingual/badge.svg" alt="TranslatePress vulnerability status"></a>