Blog

"Prevention is cheaper than a breach"

Home / Threats / CVE-2024-6386

CVE-2024-6386 - Wpml Plugin

CVE-2024-6386

The WPML plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 4.6.12 via the 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.

CVE-2024-6386

CRITICAL CVSS 9.9 Published 2024-08-21 Updated 2024-09-27
AI Risk Critical (99/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P1 Immediate
Severity Band CRITICAL
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Affected Components 1
Reference Links 3
AI Risk Engine Critical (99/100)
Exploitability High
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2024-08-21 CVE published and first recorded in the threat feed.
  2. 2024-09-27 Record updated with latest vulnerability metadata.
  3. 2026-04-09 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 12 days ago

AI enriched 12 days ago (2026-04-09 07:45 UTC)

Technical Summary

The WPML plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 4.6.12 via the 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.

Potential Impact

Severity is CRITICAL (CVSS 9.9). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as High based on remote code execution potential.

Primary risk drivers: remote code execution potential

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Wpml PLUGIN · wpml Affected: < 4.6.13 Fixed in: 4.6.13
Scroll to top