# CVE-2024-34762: Wordpress Advanced Custom Fields Pro plugin < 6.2.10 - Contributor+ Local File Inclusion vulnerability

> Contributors can exploit a path traversal flaw in Advanced Custom Fields PRO to perform local file inclusion, potentially reading sensitive files or executing code.

- **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:** 10 Jun 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-9p58-3xxv-43mc

## What is CVE-2024-34762?

CVE-2024-34762 is a critical path traversal vulnerability in WPENGINE INC Advanced Custom Fields PRO, published on 10 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vulnerability discovered by executing a planned security audit.

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in WPENGINE INC Advanced Custom Fields PRO allows PHP Local File Inclusion.This issue affects Advanced Custom Fields PRO: from n/a before 6.2.10.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2024-34762 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-34762 is a critical path traversal vulnerability in WPENGINE INC Advanced Custom Fields PRO, published on 10 Jun 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-34762 exists.

Affected product: WPENGINE INC Advanced Custom Fields PRO. 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-34762/ (Markdown: https://insights.sbomify.com/CVE-2024-34762/index.md)
```

## Sources

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

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