Skip to main content

Weglot WordPress CVE-2026-88784

| EUVDEUVD-2026-107088 HIGH
Cross-site Scripting (XSS) (CWE-79)
2026-10-21 WPScan GHSA-v5cq-8fvv-9wcc
7.5
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Submit crafted URL to translatable page content
  2. Delivery
    Plugin stores URL and reverses its encoding
  3. Exploit
    Victim loads page in translated language
  4. Execution
    Unescaped payload renders as live script
  5. Persist
    Script executes in victim browser
  6. Impact
    Session/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.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

Translate WordPress with Weglot 2.0 0 <6.4.3

Affected Packages

euvd translate_wordpress_with_weglot_2_0 fix: 6.4.3

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

Vendor (WPScan) PRIMARY 7.5 HIGH
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
vuln.today AI 4.7 MEDIUM

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.

3.1 AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N
4.0 AV:N/AC:H/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
CVSS changed
Oct 21, 2026 - 11:22 NVD
7.5 (HIGH)
Patch available
Oct 21, 2026 - 07:01 EUVD
CVE Published
Oct 21, 2026 - 06:00 cve.org
HIGH 7.5
CVE Published
Oct 21, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.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

Why It Matters

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.

Business Impact: High
Compensating Controls

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

EPSS Score
0.2%
Top 94% exploitable
Prevalence
Medium
popular WordPress translation plugin, common but not universally deployed
Exploit
POC
Public exploit code exists
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

58
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy