Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconRegister low-privilege Subscriber account
-
DeliveryObtain exposed valid nonce from handler
-
ExploitPOST crafted term translation (no capability check)
-
InstallPayload stored unescaped
-
C2Administrator views affected admin page
-
ExecuteScript executes in admin session
-
ImpactAccount takeover / site compromise
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 an authenticated account at Subscriber level or above on the target WordPress site (PR:L), so the realistic precondition is a site that permits user registration (or an attacker who already holds any low-tier account). The attacker specifically leverages the plugin's unprotected term-translation save handler, which (a) performs no capability check and (b) leaks a valid nonce to any logged-in user, letting a low-privilege user store content. Triggering the payload requires a higher-privileged user (e.g., an administrator) to view the injected term translation (UI:R), so there is no zero-click impact. Limiting factors: closed-registration sites without low-privilege accounts, and the dependency on an admin actually opening the affected screen, both meaningfully reduce exploitability below the raw 8.0 score. Fixed in version 1.4.6. |
| Impact | This is a stored XSS (CWE-79) in the Falang multilanguage WordPress plugin before 1.4.6. The input CVSS vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H, score 8.0) indicates network-reachable, low-complexity exploitation requiring only low privileges (PR:L = Subscriber and above) plus user interaction (UI:R, a higher-privileged user must view the injected content). Publicly available exploit code exists (reported by WPScan), which raises practical risk, but there is NO CISA KEV listing and NO EPSS score in the provided data, so there is no evidence of active, widespread exploitation - exploitation status is 'publicly available exploit code exists,' not confirmed in-the-wild use. Two signals conflict with the headline severity: (1) the input vector rates C:H/I:H/A:H, which is aggressive for a stored XSS whose realistic worst case is admin-session hijack / account takeover rather than guaranteed full confidentiality-integrity-availability loss, and (2) scope is marked S:U despite the payload executing in a different user's (admin's) browser context, which normally justifies S:C. Net: a genuine, actionable medium-to-high priority for sites running this plugin that accept untrusted Subscriber registrations, but the 8.0 score likely overstates direct technical impact; prioritize patching where open user registration is enabled. |
| Exploit ScenarioDerived | A site allows open registration, so an attacker signs up for a Subscriber account, then uses the exposed valid nonce and the unprotected term-translation save handler (which performs no capability check) to store a malicious XSS payload. When an administrator later views the affected term/translation screen in wp-admin, the unescaped payload executes in their authenticated session, enabling actions such as creating a rogue admin or planting a backdoor. A public exploit is available via WPScan, lowering the barrier to weaponization. |
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 Falang Multilanguage plugin for WordPress before 1.4.6 lets any authenticated user at Subscriber level or above plant script-bearing content that later renders in an administrator's browser session. The plugin's term-translation save handler performs no capability check and hands a valid nonce to any logged-in user, so a low-privilege account is enough to store the payload; execution still depends on a higher-privileged user opening the affected translation screen, which limits the real-world blast radius below the headline 8.0 score. Publicly available exploit code exists and the flaw is fixed in 1.4.6, but exploitation is only realistic on sites that allow self-registration or where the attacker already holds a low-tier account.
RemediationAI
Upgrade the Falang Multilanguage plugin to version 1.4.6 or later - this is the vendor-released patch and the only complete fix, since it adds the missing capability check on the term-translation save handler and closes the nonce exposure path; verify the version in the plugin file header after updating and re-save any existing term translations to flush stale stored payloads. If immediate patching is not possible, the highest-value compensating control is to disable public user registration and remove or demote existing Subscriber-level accounts (Settings > General > Membership), trading away self-service signup for a large reduction in attack surface; a secondary option is to deactivate the plugin entirely on sites that do not need multilingual term content, accepting loss of translated taxonomy labels. Administrators should also scan the term meta tables for injected script payloads before and after remediation, since patching does not clean already-stored content, and can add a WAF rule blocking script tags in the plugin's term-translation save requests as a stopgap - noting that such rules only block new injections and can be bypassed by encoding tricks. Full technical detail is in the WPScan advisory at https://wpscan.com/vulnerability/a7576e78-1fec-42fb-9c50-89b80e44fbc2/.
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
Falang is a multilingual content-management plugin that extends WordPress with per-post and per-term translations, storing those strings in taxonomy term meta and rendering them through the plugin's own admin and front-end templates. The root cause is CWE-79 combined with a missing authorization check: the term-translation save routine does not call current_user_can() against the relevant capability (for example manage_categories or a plugin-specific capability) and its handler is reachable by any logged-in user, including Subscribers, while also emitting a valid nonce to those users. That defeats the usual WordPress nonce-plus-capability pairing, which is designed to ensure both intent (nonce) and authority (capability). Because the stored translation strings are later echoed into admin translation screens without esc_html()/esc_attr() or wp_kses() sanitization, attacker-controlled markup is persisted in the database and executed in the DOM of whichever privileged user views it. The CPE entry (cpe:2.3:a:unknown:falang_multilanguage_for_wordpress) has no resolved vendor and a wildcard version, so version fingerprinting must come from the plugin file header or the vendor advisory rather than the CPE. The assessed vector uses scope-changed (S:C) because the script executes in the security context of a higher-privileged victim, but impact is scored as limited confidentiality and integrity (C:L/I:L) since the payload runs in the victim's browser session rather than granting direct server-side control.
Know when Falang Multilanguage For Wordpress 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:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Network-reachable with only Subscriber auth (PR:L) and admin viewing required (UI:R); stored XSS crosses into the victim's browser (S:C) with limited confidentiality/integrity impact and no availability loss.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The Falang multilanguage for WordPress plugin before 1.4.6 does not perform a capability check when saving term translations, and exposes a valid nonce to any logged-in user through an unprotected handler, allowing users with Subscriber-level access and above to store content that is later output without proper escaping, leading to Stored Cross-Site Scripting that executes in the context of higher-privileged users such as administrators.
Technical POC Analysis
CWE-79 (Stored Cross-Site Scripting), in the Falang multilanguage plugin's term-translation save path.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Executive ViewAI
The Falang Multilanguage plugin for WordPress before 1.4.6 allows a Subscriber-level account to plant script-bearing translation content that executes when an administrator opens the affected screen, creating a potential admin-session compromise on affected sites. Publicly available exploit code exists, but practical exposure is concentrated on sites that allow self-registration or already have low-tier accounts. Leadership should prioritize those sites because a compromised administrator session can affect site integrity and customer trust, while closed-membership sites have lower near-term risk despite the high severity score.
Apply vendor patch.
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-107052
GHSA-r8cc-m979-hm23
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB