CVE-2026-12428: CWE-862 Missing Authorization in gamaup Blocks for ACF Fields — Display Custom Fields in the Block Editor
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.
AI Analysis
Technical Summary
CVE-2026-12428 is a missing authorization vulnerability (CWE-862) in the Blocks for ACF Fields WordPress plugin. The vulnerability arises because the permission check on the /wp-json/acf-field-blocks/v1/values REST endpoint only verifies the generic publish_posts capability, which is insufficient. The handler function uses a user-supplied id parameter directly in get_field_objects() without verifying the user's authorization to access the targeted post or object. Consequently, authenticated users with Author-level permissions or higher can retrieve ACF field values from arbitrary posts, including private and draft posts belonging to other users.
Potential Impact
An attacker with Author-level or higher privileges can access sensitive custom field data from posts they do not own or should not access. This can lead to unauthorized disclosure of potentially sensitive information stored in ACF fields. The vulnerability does not affect integrity or availability but has a high confidentiality impact. There are no known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict Author-level access to trusted users only and monitor for suspicious activity. Avoid exposing sensitive data in ACF fields accessible via this plugin's REST endpoint.
CVE-2026-12428: CWE-862 Missing Authorization in gamaup Blocks for ACF Fields — Display Custom Fields in the Block Editor
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.
CVSS v3.1
Score 6.5medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-12428 is a missing authorization vulnerability (CWE-862) in the Blocks for ACF Fields WordPress plugin. The vulnerability arises because the permission check on the /wp-json/acf-field-blocks/v1/values REST endpoint only verifies the generic publish_posts capability, which is insufficient. The handler function uses a user-supplied id parameter directly in get_field_objects() without verifying the user's authorization to access the targeted post or object. Consequently, authenticated users with Author-level permissions or higher can retrieve ACF field values from arbitrary posts, including private and draft posts belonging to other users.
Potential Impact
An attacker with Author-level or higher privileges can access sensitive custom field data from posts they do not own or should not access. This can lead to unauthorized disclosure of potentially sensitive information stored in ACF fields. The vulnerability does not affect integrity or availability but has a high confidentiality impact. There are no known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict Author-level access to trusted users only and monitor for suspicious activity. Avoid exposing sensitive data in ACF fields accessible via this plugin's REST endpoint.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-06-16T17:09:56.538Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a4f797f68715ace432894bf
Added to database: 07/09/2026, 10:35:43 UTC
Last enriched: 07/09/2026, 10:49:07 UTC
Last updated: 07/09/2026, 19:30:04 UTC
Views: 9
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.