CVE-2024-6386: The WPML plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 4.6

Q: How do I fix CVE-2024-6386?

wpml: upgrade to 4.6.13. Exact commands for each OS are on this page.

Q: Is CVE-2024-6386 being exploited?

CVE-2024-6386 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2024-6386 affect?

CVE-2024-6386 affects wpml. Severity is critical (CVSS 9.9). 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

Q: How urgent is CVE-2024-6386?

Priority 64/100. Critical severity; EPSS top 2%: very likely to be exploited; Public exploit reference

This week

CRITICAL 9.9UPGRADE

CVE-2024-6386 is a critical-severity flaw (CVSS 9.9) affecting wpml. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Critical severity
EPSS top 2%: very likely to be exploited
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	9.9 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	25.5% (top 2%)
CISA exploited list	No
Weakness	CWE-1336, CWE-94
Published	2024-08-21
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: wpml

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-08-21 21:15 UTCPublished CVE record published
2026-06-17 08:17 UTCUpdated Record last modified

wpml wpml UPGRADE

Affected: < 4.6.13

Fixed in: 4.6.13

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wpml || rpm -q wpml || wpml --version

2. UPGRADE to 4.6.13 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wpml

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wpml

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-6386?

wpml: upgrade to 4.6.13. Exact commands for each OS are on this page.

Is CVE-2024-6386 being exploited?

CVE-2024-6386 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-6386 affect?

CVE-2024-6386 affects wpml. Severity is critical (CVSS 9.9). 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

How urgent is CVE-2024-6386?

Priority 64/100. Critical severity; EPSS top 2%: very likely to be exploited; Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2025-3488 MEDIUM 6.4 UPGRADE The WPML plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's wpml_language_swit

References

← Back to latest CVEs