ACF to REST API Plugin up to 3.3.4 on WordPress update_item_permissions_check ID resource injection

Summaryinfo

A vulnerability was found in ACF to REST API Plugin up to 3.3.4 on WordPress. It has been rated as problematic. The affected element is the function update_item_permissions_check. This manipulation of the argument ID causes resource injection. The identification of this vulnerability is CVE-2025-12030. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in ACF to REST API Plugin up to 3.3.4 on WordPress. It has been declared as problematic. Affected by this vulnerability is the function update_item_permissions_check. The manipulation of the argument id with an unknown input leads to a resource injection vulnerability. The CWE definition for the vulnerability is CWE-99. The product receives input from an upstream component, but it does not restrict or incorrectly restricts the input before it is used as an identifier for a resource that may be outside the intended sphere of control. As an impact it is known to affect integrity. The summary by CVE is:

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.

The advisory is shared at wordfence.com. This vulnerability is known as CVE-2025-12030. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/07/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• WordPress Plugin

Name

• ACF to REST API Plugin

Version

• 3.3.0
• 3.3.1
• 3.3.2
• 3.3.3
• 3.3.4

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion