WordPress News
Advanced Custom Fields (ACF®) 6.8.12 Released
What’s new in Advanced Custom Fields (ACF®) 6.8.12
Released: 2026-11-19
Active installations: 2,000,000
Tested up to WordPress 7.1.5
Requires PHP 7.4
Changelog
- Security – script tags in ACF Block preview HTML, including ones that load an external file, no longer run in the block editor unless the block opts in with allowDangerousPreviewScripts in block.json (or allow_dangerous_preview_scripts in acf_register_block_type()), or the site opts in with the new acf/blocks/allow_dangerous_preview_scripts filter
- Security – The [acf] shortcode no longer shows fields from draft or private posts referenced by a prefixed ID such as post_123 when used inside an ACF Block, or outside the loop such as in a widget on a 404 or search page
- Security – Icon Picker fields set to return an icon string no longer reveal the URLs of private Media Library images in the REST API
- New – ACF now has a new Settings page with a Features tab for turning ACF features on and off without code. In ACF PRO, the License and Updates screens are now tabs on this page. Settings defined in code are shown as “Managed via code” and can’t be changed in the UI
- New – Developers can add their own tabs, sections and fields to the Settings page with the new acf/settings_page/tabs, acf/settings_page/general/sections and acf/settings_page/general/{$section}/fields filters. The Features tab can be hidden with the new acf/settings/show_settings filter
- New – ACF Abilities are now enabled by default for all field groups, post types and taxonomies on WordPress 6.9 and later. They can be turned off for each object, or for the whole site from the Settings page. The enable_acf_ai setting has been renamed to enable_abilities, and existing allow_ai_access values are not carried over
- Enhancement – The “Edit Block” button text on ACF Blocks V3 that turn off the preview with “renderPreview”: false can now be changed with acf.placeholderButtonText in block.json or the new acf/blocks/default_placeholder_button_text filter
- New – ACF Blocks registered with acf_register_block_type() can now set the InnerBlocks default_block and direct_insert options
- Enhancement – ACF Abilities now publish valid JSON Schema, so MCP clients such as ChatGPT can discover and use them. Schemas now describe conditional logic, Repeater and Group sub fields, and Flexible Content layouts
- Enhancement – Breaking change: generated post type and taxonomy ability names now include the object type, so they no longer collide. For example, acf/create-book is now acf/create-book-post and acf/books is now acf/list-book-posts. Agent prompts and MCP configurations that use the old names need updating
- Enhancement – The acf/field-groups Ability now includes the list of fields within each field group
- Enhancement – The Date Picker field’s bundled jQuery UI stylesheet has been updated to version 1.14.2
Previous releases
6.8.11
- Security – Custom values submitted to Checkbox, Radio, and Select fields with “Save Custom Values” enabled can no longer corrupt the field’s settings or add HTML attributes to the field’s wrapper. The new acf/fields/allow_append_choices filter can be used to restrict who can add new choices to a field. Thanks to Jakub Herman via WPScan for the responsible disclosure
- Security – ACF now sanitizes field, field group, post type, taxonomy, and options page settings saved by users without the unfiltered_html capability. For those users, a field’s wrapper settings are limited to width, class, and id. Event handler (on*) attributes in a field’s wrapper setting are no longer output for any field, including fields registered in PHP or local JSON
- Security – Field values of password-protected posts are no longer shown by the [acf] shortcode, block bindings, JSON-LD output, or the REST API until the password is entered. REST responses also no longer expand a referenced password-protected post into a full post object
- Security – The [acf] shortcode and ACF block bindings now output only user IDs for User fields, rather than personal data such as names and email addresses. The previous output can be restored with the new acf/bindings/allow_user_data filter
- Security – Files uploaded through the basic uploader by users without the upload_files capability no longer generate PDF preview images or save embedded audio and video cover art. This can be changed with the new acf/upload/generate_previews filter
6.8.10
- Security – ACF now validates that uploaded PDF files begin with the standard %PDF- header before further processing, rejecting files that do not match the expected format
- Security – The Relationship, Post Object, Image, Gallery, and File fields now enforce WordPress read permissions on referenced posts and attachments when returned in REST API responses
- Security – ACF now verifies both preview context and the caller’s edit capability before substituting revision data when field values are retrieved for a post
- Security – The _acf_form token used by frontend forms now expires and is bound to its issuing render, and acf_encrypt() / acf_decrypt() gain an optional $context argument for domain separation between token uses
- Security – ACF now consistently runs field validation on frontend form submissions containing field data, ensuring required-field checks and custom acf/validate_value filters cannot be circumvented