What the vulnerability does
01Description
The Blocks for ACF Fields plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the get_all_values() function in the /wp-json/acf-field-blocks/v1/values REST endpoint in versions up to, and including, 1.6.2. The permission_callback only verifies the generic publish_posts capability and the handler passes a user-supplied id parameter directly to get_field_objects() without verifying that the requesting user is authorized to read the target object. This makes it possible for authenticated attackers, with Author-level access and above, to read ACF field values from arbitrary posts (including private posts, drafts, posts by other users, and other ACF-supported objects) that they should not have access to.
Explanation of Vulnerability in Simple Terms
02Summary
Blocks for ACF Fields versions 1.6.2 and earlier do not properly check user permissions before allowing access to custom field data. A logged-in user with low privileges can read sensitive custom fields they should not have access to. Update to a version newer than 1.6.2.
What an attacker can do
03Attacker Capabilities
Read custom field data that should be restricted to higher-privilege users.
Potential impact on your site
04Site Impact
Sensitive custom field data may be exposed to low-privilege users, potentially including private client or business information.
Conditions required to exploit
05Prerequisites
Attacker must have a low-privilege WordPress account (e.g., subscriber or contributor).
Key dates
06Disclosure timeline
July 9, 2026
CVE published
July 9, 2026
Record updated
