# CVE-2012-10025: WordPress Plugin Advanced Custom Fields <= 3.5.1 Remote File Inclusion

> Unauthenticated attackers can execute arbitrary code via remote file inclusion if allow_url_include is enabled, compromising the web server.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2025
- **Updated:** 15 May 2026
- **Also known as:** GHSA-h43p-j9xg-vxvr

## What is CVE-2012-10025?

CVE-2012-10025 is a critical code injection vulnerability in Advanced Custom Fields WordPress Plugin, published on 5 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WordPress plugin Advanced Custom Fields (ACF) version 3.5.1 and below contains a remote file inclusion (RFI) vulnerability in core/actions/export.php. When the PHP configuration directive allow_url_include is enabled (default: Off), an unauthenticated attacker can exploit the acf_abspath POST parameter to include and execute arbitrary remote PHP code. This leads to remote code execution under the web server’s context, allowing full compromise of the host.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

## Which versions are affected by CVE-2012-10025?


## How do I fix CVE-2012-10025?

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

## Is CVE-2012-10025 being exploited?

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

Public exploit code:

- WordPress Plugin Advanced Custom Fields Remote File Inclusion (metasploit)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-10025 and fix it if it is affected.

What it is: CVE-2012-10025 is a critical code injection vulnerability in Advanced Custom Fields WordPress Plugin, published on 5 Aug 2025. 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-2012-10025 exists.

Affected product: Advanced Custom Fields WordPress Plugin. 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-2012-10025/ (Markdown: https://insights.sbomify.com/CVE-2012-10025/index.md)
```

## Sources

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

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