# CVE-2024-6386: Code injection in WPML

> Authenticated attackers with Contributor access can execute arbitrary code on the server via Twig Server-Side Template Injection in the WPML plugin.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-q8gr-qpfg-hv8p

## What is CVE-2024-6386?

CVE-2024-6386 is a critical code injection vulnerability in WPML, published on 21 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

## Which versions are affected by CVE-2024-6386?

It affects 1 product.


Products: Wpml Wpml.

## How do I fix CVE-2024-6386?

No fix has been published for CVE-2024-6386 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-6386 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6386 exists.

Public exploit code:

- Research and PoC for CVE-2024-6386 (github_poc): https://github.com/argendo/CVE-2024-6386
- https://github.com/bananoname/CVE-2024-6386-WPML-SSTI (github_poc): https://github.com/bananoname/CVE-2024-6386-WPML-SSTI

## Other vulnerabilities in WPML

- [CVE-2015-2792](https://insights.sbomify.com/CVE-2015-2792/): Security feature bypass in n/a (high 7.5)
- [CVE-2015-2314](https://insights.sbomify.com/CVE-2015-2314/): SQL injection in n/a (high 7.5)
- [CVE-2025-3488](https://insights.sbomify.com/CVE-2025-3488/): Cross-site scripting in WPML (medium 6.4)
- [CVE-2015-2791](https://insights.sbomify.com/CVE-2015-2791/): Missing authorization in n/a (medium 6.4)
- [CVE-2018-18069](https://insights.sbomify.com/CVE-2018-18069/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-6386 and fix it if it is affected.

What it is: CVE-2024-6386 is a critical code injection vulnerability in WPML, published on 21 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6386 exists.

Affected product: WPML. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-6386/ (Markdown: https://insights.sbomify.com/CVE-2024-6386/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-6386
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-6386
- OSV: https://osv.dev/vulnerability/CVE-2024-6386

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-6386/
Summaries are generated and may contain mistakes; the official description above is the record.