Skip to main content
CVE-2026-125053VulnerabilityPublished

The WEB-Translation – eTranslation Multilingual plugin for WordPress is vulnerable to Stored Cross-Site Scripting via

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-125053· High 7.2

Not known to be exploited · CVSS 7.2 High.

Data as of 18 Nov 2026, 17:04 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.17.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
ecwebtWEB-Translation – eTranslation MultilingualAffected
  • <=2.0.7
Fixed in–

AI-suggested

Until a fix is available, administrators should consider disabling comments or secondary languages in the plugin as a temporary mitigation to reduce exposure. Monitoring vendor channels for updates is recommended.

Description

The WEB-Translation – eTranslation Multilingual plugin for WordPress versions up to and including 2.0.7 is vulnerable to a stored cross-site scripting (XSS) flaw via the 'comment' parameter. This vulnerability arises from insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject malicious scripts that execute when users visit affected pages under a secondary-language URL. Exploitation requires at least one secondary language configured and open comments on the target post. The payload bypasses WordPress core KSES filtering because it contains no literal HTML brackets at save-time, materializing only when the post is viewed in the secondary language.

References

Community reviews

Loading reviews…