Approved changes feed: RSS · Atom

cpe:2.3:a:cozmoslabs:translatepress_–_translate_multilingual_sites_with_ai_translation:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorCozmoslabs (a6cf7c48-9910-5089-9ac0-ffa6c9be99f9)
ProductTranslatepress – Translate Multilingual Sites With Ai Translation (e1476a6e-d0ce-56f2-9f28-623602439af1)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*

Notes

Imported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-107768 vulnerable 2026-11-03 10:15:59.501859 TranslatePress <= 3.3.7 - Unauthenticated Stored Cross-Site Scripting via Comment Anchor href with trp-gettext/TRPLINKPROCESSED Markers
HIGH (7.2)
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.
Published: 2026-10-16T06:41:04.583Z
Updated: 2026-10-16T14:39:02.658Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-89412 vulnerable 2026-10-13 12:29:55.002014 TranslatePress <= 3.3.5 - Unauthenticated Stored Cross-Site Scripting via Translation Memory Suggestion Panel
HIGH (7.2)
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.
Published: 2026-09-22T06:39:40.880Z
Updated: 2026-09-23T18:46:53.988Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-18510 vulnerable 2026-09-16 04:34:02.232227 TranslatePress <= 3.2.6 - Unauthenticated Stored Cross-Site Scripting via Comment Content
HIGH (7.2)
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.
Published: 2026-08-06T05:29:25.581Z
Updated: 2026-08-06T15:37:16.079Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-17505 vulnerable 2026-09-16 04:33:02.802489 TranslatePress <= 3.2.5 - Reflected Cross-Site Scripting
MEDIUM (6.1)
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.
Published: 2026-08-05T06:37:57.133Z
Updated: 2026-08-05T15:55:10.726Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.