WordPress security changelog
MEDIUM CVE-2026-12428 Deferred

Blocks for ACF Fields — Display Custom Fields in the Block Editor: A security weakness

Blocks for ACF Fields — Display Custom Fields in the Block Editor is affected by a security weakness. Exploitation requires at least author-level access. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is <= 1.6.2.

CVE / CNA score 6.5 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Blocks for ACF Fields — Display Custom Fields in the Block Editor
Plugin slug
acf-field-blocks
Affected
<= 1.6.2
Safe version
> 1.6.2
Published
Jul 09, 2026
Weakness
CWE-862 — Missing Authorization

This CVE was published Jul 09, 2026 and is one of 1 known issue for this plugin.

What to do

Update, patch or deactivate.

Update Blocks for ACF Fields — Display Custom Fields in the Block Editor to a release after 1.6.2, or disable and remove it until a fixed version is available.

A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical 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.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

References

Primary and upstream sources