Description
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.
References8
- plugins.trac.wordpress.org/browser/acf-field-blocks/tags/1.5.0/…
- plugins.trac.wordpress.org/browser/acf-field-blocks/tags/1.5.0/…
- plugins.trac.wordpress.org/browser/acf-field-blocks/tags/1.5.0/…
- plugins.trac.wordpress.org/browser/acf-field-blocks/tags/1.6.0/…
- plugins.trac.wordpress.org/browser/acf-field-blocks/tags/1.6.0/…
- plugins.trac.wordpress.org/browser/acf-field-blocks/tags/1.6.0/…
- plugins.trac.wordpress.org/changeset?reponame=&old=3587876%40ac…
- www.wordfence.com/threat-intel/vulnerabilities/id/fc48f75d-a2e8…
Metrics
- CVSS 3.1
-
6.5
MEDIUM
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N - EPSS — exploit probability
- 0% percentile: 42 · as of 15 November 2026
- CWE
- CWE-862
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.