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.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
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
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.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
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: 1 proofs of concept on GitHub.
Sources
Also known as GHSA-g9gc-23hp-3qj2.