Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSubmit crafted URL to translatable page content
-
DeliveryPlugin stores URL and reverses its encoding
-
ExploitVictim loads page in translated language
-
ExecutionUnescaped payload renders as live script
-
PersistScript executes in victim browser
-
ImpactSession/credential theft or forced admin action
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the site to be running the Translate WordPress with Weglot 2.0 plugin (before 6.4.3) with at least one additional translated language configured and the link-rewriting/translation rendering feature active - the flaw only triggers when the plugin re-inserts and rewrites URLs for a translated-language view. The specific prerequisite from the description is that the plugin does not escape re-inserted URLs AND reverses their prior encoding during link rewriting, so the stored payload only fires when a victim loads the page in a translated language. Limiting factors: required user interaction (a victim must view the translated version of the page, UI:R), high attack complexity (AC:H) reflecting the non-trivial encoding-reversal condition, and impact confined to the browser context of whoever views the page. No authentication is needed to plant the payload (PR:N). |
| Impact | This is a genuine but moderate-priority issue rather than a critical fire-drill. The provided CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:R) describes an unauthenticated, network-reachable stored XSS that nonetheless requires both high attack complexity and victim interaction (viewing a page in a translated language), which meaningfully constrains reliable exploitation. The C:H/I:H/A:H impact metrics assigned upstream (WPScan) are aggressive for a browser-context XSS and appear inflated - a client-side script-injection flaw does not realistically yield full confidentiality/integrity/availability loss of the server, so the real-world technical impact is better characterized as limited browser-side script execution (session theft, defacement, admin action forgery if an admin views the page). Exploitation signals are mixed-to-moderate: publicly available exploit code exists (WPScan), which raises accessibility, but there is NO CISA KEV listing and NO EPSS score provided, so there is no evidence of active or widespread exploitation - treat this as a patch-in-normal-cycle item unless an administrator-facing page is the injection target. Note the tension: PR:N (unauthenticated store) combined with AC:H means anyone can plant the payload, but it only fires under the specific translated-rendering condition, pointing to opportunistic rather than mass exploitation. No EPSS or SSVC data was supplied - risk ranking below the CVSS headline should be verified against the vendor advisory. |
| Exploit ScenarioDerived | An unauthenticated attacker submits a crafted URL into content (e.g. a comment, profile, or other field re-inserted as a link) that the Weglot plugin later rewrites for a translated language; because the plugin fails to escape the re-inserted URL and reverses the prior encoding, the payload is stored and rendered as live markup. When any visitor - potentially a logged-in administrator - views the affected page in a translated language, the script executes in their browser, enabling session hijacking or actions on their behalf. Public exploit code from WPScan lowers the barrier to reproducing this, though the high attack complexity and required victim view limit reliability. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Stored cross-site scripting in the Weglot WordPress plugin before 6.4.3 lets unauthenticated attackers plant a payload that executes in the browser of anyone who views an affected page in a translated language. The flaw appears when Weglot rewrites links for translated content: it re-inserts URLs without escaping and reverses earlier encoding. Exploitation requires the site to have link rewriting/translation rendering active with at least one additional language and a victim to load the translated view; publicly available exploit code exists, and the issue is moderate priority rather than a critical fire-drill.
RemediationAI
Upgrade to Weglot 6.4.3 or later; the vendor-released patch is 6.4.3, with details in the WPScan advisory at https://wpscan.com/vulnerability/0a567730-5dd9-4bcb-b955-312979041466/. If immediate update is not possible, disable the plugin's automatic link rewriting and translated-language rendering until patched, or temporarily remove additional translated languages; this breaks translated navigation and localized page views but removes the vulnerable re-insertion path. As compensating controls, restrict untrusted users from submitting content that can introduce URLs into translated pages and deploy WAF rules that inspect translated-page requests for encoded script payloads in URL parameters; these reduce exposure but do not remediate stored payloads already present, so audit and clean affected translated content after upgrading.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The Weglot plugin integrates WordPress with Weglot translation and rewrites links so translated pages point to the correct localized URLs. During that link-rewriting path, the plugin takes URLs that were previously encoded, reverses that encoding, and re-inserts them into the page without output escaping. That violates CWE-79: an attacker can supply a URL containing script content, and when the page is rendered in a translated language the browser parses the re-inserted value as executable markup. The affected CPE identifies translate_wordpress_with_weglot_2.0, and EUVD lists versions before 6.4.3. The independent assessment confines impact to the browser context (low confidentiality/integrity, no availability) and notes AC:H/UI:R/PR:N, reflecting the encoding-reversal precondition and the need for a victim to view the translated page.
Know when Translate Wordpress With Weglot 2 0 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Unauthenticated stored XSS (PR:N) firing only on translated rendering with victim view, so AC:H and UI:R; browser-context execution crosses into the user's session so S:C with limited C:L/I:L and no availability impact.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The Translate WordPress with Weglot 2.0 WordPress plugin before 6.4.3 does not escape the URLs it re-inserts into a page when rewriting links for a translated language, and reverses the encoding that was applied to them beforehand, allowing unauthenticated users to store a payload which executes in the browser of anyone viewing the page in a translated language.
Technical POC Analysis
CWE-79 (stored cross-site scripting), in the Weglot WordPress plugin's translated-page link rewriting path.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
WordPress sites running the Weglot translation plugin below version 6.4.3 are exposed to a stored cross-site scripting flaw that can run attacker-controlled code in the browsers of visitors viewing translated pages. The payload persists on affected pages and is delivered to any visitor of a translated language view, putting visitor trust, session integrity, and site reputation at risk rather than back-end systems. Leadership should prioritize a low-effort plugin update because publicly available exploit code exists.
Apply vendor patch (Weglot 6.4.3 or later). If immediate patching is not possible, disable Weglot link rewriting and remove additional translated languages until the update is applied.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
EUVD-2026-107088
GHSA-v5cq-8fvv-9wcc
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB