# CVE-2024-6460: Grow by Tradedoubler <= 2.0.21 - Unauthenticated LFI

> Unauthenticated attackers can exploit a Local File Inclusion vulnerability in the Grow by Tradedoubler WordPress plugin to execute arbitrary PHP code on the server.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Aug 2024
- **Updated:** 13 Sep 2024
- **Also known as:** GHSA-x4r5-v2mq-hx64

## What is CVE-2024-6460?

CVE-2024-6460 is a critical path traversal vulnerability in Unknown Grow by Tradedoubler, published on 16 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Grow by Tradedoubler  WordPress plugin through 2.0.21 is vulnerable to Local File Inclusion via the component parameter. This makes it possible for attackers to include and execute PHP files on the server, allowing the execution of any PHP code in those files.

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

It affects 1 product.


Products: Tradedoubler Grow.

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

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

## Is CVE-2024-6460 being exploited?

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

Public exploit code:

- Grow by Tradedoubler < 2.0.22 - Unauthenticated LFI (github_poc): https://github.com/Nxploited/CVE-2024-6460
- 备份的CVE (github_poc): https://github.com/E1-Bot141/CVE-2024-6460
- WordPress Grow by Tradedoubler Plugin < 2.0.22 - Unauthenticated Local File Inclusion (nuclei): http/cves/2024/CVE-2024-6460.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2024-6460 is a critical path traversal vulnerability in Unknown Grow by Tradedoubler, published on 16 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6460 exists.

Affected product: Unknown Grow by Tradedoubler. 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-6460/ (Markdown: https://insights.sbomify.com/CVE-2024-6460/index.md)
```

## Sources

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

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