Plugins · acf-field-blocks · data as of 2026-11-04
Is Blocks for ACF Fields safe? Known vulnerabilities and latest version
- Latest version
- 1.6.6
- Last updated
- 2026-11-02
- Active installs
- 2,000+
- Known issues on record
- 1
- Unpatched in latest
- 0
- Tested up to WP
- 7.1.4 · PHP 7.4+
The easiest way to load ACF & SCF fields in WordPress blocks. Add your custom fields to the block editor instantly — no coding required! — by gamaup
What to do
- Update to the latest version (1.6.6). Anything older than 1.6.3 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get acf-field-blocks --field=version shows what you run; wp plugin update acf-field-blocks updates it.
Check your version
Known vulnerabilities
1 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
medium 6.5 CVE-2026-12428 · published 2026-07-09
Missing authorization check in Blocks for ACF Fields (1.6.2 and older)
- Affected
- 1.6.2 and older
- Fixed in
- 1.6.3 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber)
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
NVD CVE-2026-12428Wordfence advisoryCode change (fix)Plugin source
Recent activity
- 2026-11-02 — latest release on wordpress.org (1.6.6).
- 2026-07-09 — Missing authorization check disclosed (CVE-2026-12428), fixed in 1.6.3.
Get an email when Blocks for ACF Fields has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Blocks for ACF Fields (acf-field-blocks) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Missing authorization (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/acf-field-blocks (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/acf-field-blocks"><img src="https://laskyr.com/plugins/acf-field-blocks/badge.svg" alt="Blocks for ACF Fields vulnerability status"></a>