CVE-2024-6386

WPML Multilingual CMS <= 4.6.12 - Authenticated (Contributor+) Remote Code Execution via Twig Server-Side Template Injection

2024-08-21 08:00
stealthcopter

Strategic Overview

Status
Patched in 4.6.13
Affected Plugin
WPML Multilingual CMS
Affected Version
<= 4.6.12
CVSS
9.9Critical
Weakness type
CWE-1336 · Improper Neutralization of Special Elements Used in a Template Engine
CVE
CVE-2024-6386
View all WPML Multilingual CMS vulnerabilities

At a glance

CVE-2024-6386 is a critical-severity Improper Neutralization of Special Elements Used in a Template Engine vulnerability in the WPML Multilingual CMS WordPress plugin, affecting versions <= 4.6.12. It carries a CVSS score of 9.9 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 4.6.13; sites on affected versions should update now. Disclosed August 2024, reported by stealthcopter.

Vulnerability Overview

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.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-1336: Improper Neutralization of Special Elements Used in a Template Engine

The product uses a template engine to insert or process externally-influenced input, but it does not neutralize or incorrectly neutralizes special elements or syntax that can be interpreted as template expressions or other code directives when processed by the engine.

Remediation

Update to version 4.6.13, or a newer patched version

How does WordSec protect against this?

An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: WPML Multilingual CMS 4.6.13 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-6386https://www.wordfence.com/threat-intel/vulnerabilities/id/f7fc91cc-e529-4362-8269-bf7ee0766e1ehttps://nvd.nist.gov/vuln/detail/CVE-2024-6386

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C