# CVE-2025-12030: Missing authorization in ACF to REST API

> Authenticated contributors can modify arbitrary posts, users, and site options due to insufficient permission checks in the ACF to REST API plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **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:** 7 Jan 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-g9gc-23hp-3qj2

## What is CVE-2025-12030?

CVE-2025-12030 is a medium-severity missing authorization vulnerability in airesvsg ACF to REST API, published on 7 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The ACF to REST API plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.3.4. This is due to insufficient capability checks in the update_item_permissions_check() method, which only verifies that the current user has the edit_posts capability without checking object-specific permissions (e.g., edit_post($id), edit_user($id), manage_options). This makes it possible for authenticated attackers, with Contributor-level access and above, to modify ACF fields on posts they do not own, any user account, comments, taxonomy terms, and even the global options page via the /wp-json/acf/v3/{type}/{id} endpoints, granted they can authenticate to the site.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2025-12030?


## How do I fix CVE-2025-12030?

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

## Is CVE-2025-12030 being exploited?

There is no known exploitation of CVE-2025-12030 in the wild and no public exploit code.

Public exploit code:

- ACF to REST API WordPress Plugin IDOR Vulnerability (CVE-2025-12030) - Security flaw allowing authenticated users with Contributor-level access to modify ACF fields on objects they do not own. (github_poc): https://github.com/SnailSploit/CVE-2025-12030

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-12030 and fix it if it is affected.

What it is: CVE-2025-12030 is a medium-severity missing authorization vulnerability in airesvsg ACF to REST API, published on 7 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-12030 in the wild and no public exploit code.

Affected product: airesvsg ACF to REST API. 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-2025-12030/ (Markdown: https://insights.sbomify.com/CVE-2025-12030/index.md)
```

## Sources

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

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