WPML
CVE-2024-6386
CRITICAL
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Contributor-level WordPress account
-
DeliveryCraft post with malicious WPML shortcode
-
ExploitSubmit Twig SSTI payload to render function
-
ExecutionTwig evaluates payload server-side
-
PersistExecute arbitrary PHP as web user
-
ImpactEstablish persistence and pivot within host
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V1 - Encoding and Sanitization Template injection prevention
|
| Exploitation Conditions | Exploitation requires an authenticated WordPress account at Contributor role or higher on a site with the WPML plugin installed and activated at version 4.6.12 or earlier, and the attacker must be able to submit content containing a WPML shortcode that reaches the vulnerable Twig render path (typically post or page content where shortcodes are evaluated). No user interaction from an administrator is required (UI:N), the attack is network-reachable over normal HTTP/HTTPS to the WordPress site, and no non-default WPML configuration is needed. Sites that disable open registration and tightly control Contributor accounts materially limit exposure, while sites that allow self-service Contributor sign-up or have many low-trust authors are directly exposed. |
| Impact | Multiple signals converge on high real-world risk. The CVSS 9.9 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) indicates network-reachable, low-complexity exploitation requiring only low privileges with scope change and full CIA impact; EPSS at 73.91% (99th percentile) and publicly available exploit code reinforce that adversaries can readily weaponize the issue. The Contributor-level prerequisite is a meaningful but low bar on sites that allow user registration or guest authoring, and SSTI yielding RCE represents maximum technical impact with high automatability. The vulnerability is not currently listed in CISA KEV, so active exploitation is not confirmed - but with public PoCs and a very high EPSS score, treat this as imminent rather than theoretical. No major conflicting signals were observed in the provided data. |
| Exploit ScenarioDerived | An attacker registers or compromises a Contributor-level WordPress account on a site running WPML <= 4.6.12, then creates or edits a post that embeds a malicious WPML shortcode containing a Twig SSTI payload. When the post is previewed or published and the shortcode is rendered, Twig evaluates the payload server-side and executes attacker-chosen PHP, yielding code execution as the web server user; public PoCs make this scenario directly reproducible by low-skill adversaries. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAI
Remote code execution in the WPML WordPress multilingual plugin (versions up to and including 4.6.12) allows Contributor-level authenticated users to execute arbitrary code on the underlying server via Twig Server-Side Template Injection in the shortcode render function. Publicly available exploit code exists and EPSS rates the exploitation probability at 73.91% (99th percentile), making this a high-priority issue for any WordPress site running WPML.
RemediationAI
Upgrade WPML to version 4.6.13 or later, which the vendor released to address the Twig SSTI; cite the Wordfence Threat Intelligence advisory and the WPML release notes on wpml.org for the authoritative fix reference. Until upgrade is possible, restrict who can author content by removing or downgrading untrusted Contributor and Author accounts, temporarily disable open user registration, and audit existing low-privilege users for unexpected activity; on multisite deployments, consider deactivating WPML on lower-trust sites. As compensating controls, deploy a WAF rule that blocks Twig-style payloads (such as {{, }}, and known Twig sandbox-escape gadgets) in WPML shortcode parameters, knowing this may produce false positives on legitimate multilingual content and is not a substitute for patching.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
WPML is one of the most widely deployed multilingual plugins for WordPress, identified by CPE cpe:2.3:a:wpml:wpml:*:*:*:*:*:wordpress:*:*. The flaw is classified as CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine), specifically a Server-Side Template Injection (SSTI) flaw in WPML's use of the Twig templating engine. When user-controlled input reaches Twig's render function without sanitization, attackers can inject template syntax that Twig evaluates server-side, abusing Twig's object filters and PHP interoperability to reach arbitrary PHP execution from what is normally rendered as benign shortcode output.
Know when Wpml 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:H/I:H/A:H
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
2DescriptionCVE.org
The WPML plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 4.6.12 via Twig Server-Side Template Injection. This is due to missing input validation and sanitization on the render function. This makes it possible for authenticated attackers, with Contributor-level access and above, to execute code on the server.
Executive ViewAI
WPML, a critical WordPress multilingual plugin used across thousands of sites, contains a remote code execution vulnerability in versions up to 4.6.12 that requires only Contributor-level user access to exploit. With publicly available exploit code and a 99th percentile exploitation probability, any WordPress site running affected WPML versions faces immediate risk of unauthorized server access and site takeover. Leadership should prioritize WPML remediation as part of WordPress infrastructure hardening.
No vendor-released patch identified at time of analysis. Interim mitigations include: disable WPML plugin entirely and implement alternative multilingual solutions; restrict Contributor-level user permissions to authenticated administrators only; deploy Web Application Firewall rules targeting Twig template injection syntax; configure centralized logging to monitor for exploitation attempts; require multi-factor authentication for all publishing-capable accounts; and conduct access control review to remove unnecessary Contributor privileges.
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
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Affected Products (CPE)CVE.org
SQL injection vulnerability in the WPML plugin before 3.1.9 for WordPress allows remote attackers to execute arbitrary S
The "menu sync" function in the WPML plugin before 3.1.9 for WordPress allows remote attackers to delete arbitrary posts
The WPML plugin before 3.1.9 for WordPress does not properly handle multiple actions in a request, which allows remote a
process_forms in the WPML (aka sitepress-multilingual-cms) plugin through 3.6.3 for WordPress has XSS via any locale_fil
Cross-site scripting (XSS) vulnerability in the WPML plugin before 3.1.9 for WordPress allows remote attackers to inject
Cross-Site Request Forgery (CSRF) vulnerability in WPML Multilingual CMS premium plugin <= 4.5.13 on WordPress. Rated hi
Time-based blind SQL injection in the WPML Multilingual CMS WordPress plugin (all versions through 4.9.5) enables authen
The WPML plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's wpml_language_switcher short
Broken Access Control vulnerability in WPML Multilingual CMS premium plugin <= 4.5.10 on WordPress allows users with sub
Cross-Site Request Forgery (CSRF) vulnerability in WPML Multilingual CMS premium plugin <= 4.5.13 on WordPress. Rated me
Broken Access Control vulnerability in WPML Multilingual CMS premium plugin <= 4.5.10 on WordPress allows users with a s
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB