Blocks for ACF Fields · Security record
Is Blocks for ACF Fields safe?
No known vulnerability affects the current version (1.7.0). 1 issue was found in earlier versions and fixed, the latest disclosed on Jul 8, 2026.
Checked 3 days ago against the WPVulnerability database, for version 1.7.0.
How it’s looked after
- Last release
- Nov 7, 2026 (1 day ago)
- Releases in the last year
- 13
- Tested up to
- WordPress 7.2
- Support resolved
- 0 of 1 threads in two months
- Active installs
- 2K+
1 known vulnerability
- 1 medium
None affects the current version.
Every known vulnerability in Blocks for ACF Fields
Newest first, with any that affect the current version at the top.
Fixed in 1.6.3 · CVE-2026-12428 · Jul 8, 2026 · Wordfence
Questions about Blocks for ACF Fields’s security
Is Blocks for ACF Fields safe to use?
No known vulnerability affects its current version. Earlier versions had issues that are now fixed, so keep Blocks for ACF Fields updated: most attacks target sites that haven’t updated.
Does Blocks for ACF Fields have known security vulnerabilities?
None that affect the current version. WPVulnerability’s database lists 1 older issue, fixed in earlier versions, so keep Blocks for ACF Fields up to date.
Is Blocks for ACF Fields still maintained?
Yes. Its last release was 1 day ago. Its authors resolved 0 of the 1 support threads opened in the last two months.
Is Blocks for ACF Fields compatible with the latest WordPress?
Yes. It’s tested up to WordPress 7.2, ahead of the current 7.1.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.