CyberRota Analysis
AI-GeneratedThe Blocks for ACF Fields plugin for WordPress is vulnerable due to inadequate capability checks in the get_all_values() function, allowing authenticated users with Author-level access or higher to access sensitive ACF field values from any post, including private and draft content. This flaw poses a risk of unauthorized data exposure, potentially compromising user privacy and data integrity. WordPress site administrators using this plugin should prioritize applying updates or implementing mitigations to safeguard against unauthorized data access.
Original NVD 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.