Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Contributor+ account
-
DeliveryCraft post with malicious script in content
-
ExploitPlugin stores payload unsanitized
-
ExecutionAdmin/user views injected page
-
PersistScript runs in victim browser session
-
ImpactSession hijack or privileged actions
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 with Contributor-level capabilities or above on the target WordPress site running WP Multilang <=2.4.31, allowing the attacker to create/edit post content. The payload is stored in post content and triggers automatically (UI:N for the attacker) when any user, including higher-privileged administrators, accesses the injected page - no separate victim click on a crafted link is needed. What limits exploitation: sites that do not permit untrusted user registration at Contributor level or higher, and sites already updated past 2.4.31, are not exposed; the impact is bounded to browser-context script execution (C:L/I:L) rather than direct server compromise. |
| Impact | This is a moderate-severity stored XSS (CWE-79) with a Wordfence-assigned CVSS 3.1 score of 6.4 (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N). The network vector and low attack complexity are offset by the PR:L requirement: the attacker must already hold Contributor-level access or above, so this is not an unauthenticated internet-wide risk but rather a privilege-abuse/insider or compromised-low-privilege-account scenario. The scope change (S:C) correctly reflects that injected script executes in the browser context of any user viewing the page, including higher-privileged editors/admins, which is the real escalation path. No EPSS score, no CISA KEV listing, and no public exploit code were provided, so exploitation status is 'no public exploit identified at time of analysis.' There are no conflicting signals in the data - CVSS vector, description, and CWE are internally consistent. Net priority: a genuine but not urgent issue; patch on a normal cycle, prioritizing sites that allow untrusted Contributor/Author registrations. |
| Exploit ScenarioDerived | An attacker who has registered or obtained a Contributor-level account crafts a post whose content contains a malicious script payload that survives the plugin's insufficient sanitization. When an administrator or other user previews or views the resulting page, the script executes in their authenticated session, enabling session/nonce theft or admin actions. No public proof-of-concept was identified, and exploitation requires the attacker to already hold an authenticated low-privilege account. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 24, 2026
Stored cross-site scripting in the WP Multilang translation and multilingual plugin for WordPress (all versions up to and including 2.4.31) lets an authenticated attacker holding Contributor-level capabilities or higher inject arbitrary JavaScript into post content, which then executes in the browser of any user - including administrators - who views the affected page. The flaw is rated moderate severity at CVSS 3.1 6.4 (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) and stems from insufficient input sanitization and output escaping (CWE-79); no public exploit code and no confirmed active exploitation were identified at time of analysis, though the low attack complexity and automatic trigger on page view make it attractive for privilege-escalation and session-theft chains. Sites that do not grant untrusted users Contributor access or that have upgraded beyond 2.4.31 are not exposed.
RemediationAI
The primary fix is to update the WP Multilang plugin to a release later than 2.4.31; the vendor has published an upstream fix (Trac changeset 3637485), and because that reference is a commit rather than a tagged release, the exact patched version number should be verified on the plugin's WordPress.org page before declaring the site clean - do not assume any specific version number beyond what the vendor publishes. If an immediate upgrade is not possible, reduce exposure by removing Contributor-or-higher privileges from any account not strictly required to publish, disabling untrusted user registration and open author roles, and auditing existing post content for unexpected HTML or script elements; these controls trade flexibility for safety and do not eliminate the flaw for legitimate contributor workflows. A WAF or virtual-patching rule that blocks script markup inside post-submission requests can act as an interim compensating control, at the cost of occasional false positives on legitimate embedded media and the need to keep rule sets current. Because the payload executes when an administrator views the infected page, administrators should also review drafts and revisions from low-privileged authors before publication and invalidate active sessions if compromise is suspected; none of these workarounds are a substitute for the plugin update.
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 vulnerability is a classic persisted (stored) cross-site scripting issue, CWE-79, in the WordPress plugin ecosystem - specifically WP Multilang, tracked under CPE cpe:2.3:a:magazine3:wp_multilang_-_translation_and_multilingual_plugin:*:*:*:*:*:*:*:*. Because the plugin is a translation/multilingual layer, it processes and re-renders post content as part of its language-handling pipeline, and that content is not adequately sanitized on input or escaped on output before being stored and later rendered. The root cause class is improper neutralization of user-controllable input during page generation: data supplied through the post content field survives storage and is emitted into an HTML context without encoding, so the browser parses it as markup and script. The CVSS vector's Scope change (S:C) reflects that the injected script executes in the security context of the WordPress site's users, including administrators who view the page, rather than being confined to the attacker's own account - which is why the confidentiality and integrity impacts are rated Low individually but the cross-user reach is significant. The low PR:L value confirms the attacker needs only a Contributor-level account, the role tier WordPress grants to untrusted authors, and UI:N means the attacker does not need to lure a victim into clicking a crafted link - the payload fires automatically when the injected page is loaded.
Know when Wordpress Plugin 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:N/S:C/C:L/I:L/A:N
Authenticated Contributor+ injection (PR:L) over the network with low complexity; stored payload executes in other users' browsers (S:C) yielding limited confidentiality/integrity impact and no availability impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The WP Multilang - Translation and Multilingual Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the post content in all versions up to, and including, 2.4.31 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
EUVD-2026-85837
GHSA-x9gx-wjjg-vc2r
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB