WordPress News
Advanced Custom Fields (ACF®) 6.8.11 Released
What’s new in Advanced Custom Fields (ACF®) 6.8.11
Released: 2026-11-02
Active installations: 2,000,000
Tested up to WordPress 7.1.4
Requires PHP 7.4
Changelog
- 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
- Security – ACF now discards submitted field values unless the field was rendered for the content being saved or its field group’s location rules match it. Inputs outside these rules, such as fields added with JavaScript, can be allowed with the acf/form/{context}/allowed_field_keys and acf/options_page/allowed_field_keys filters. Registration forms no longer save fields from field groups set to “User Form is Add / Edit”. Thanks to vuxvinh via WPScan for the responsible disclosure
- Security – WordPress’s Custom Fields meta box, its AJAX handler, and XML-RPC can no longer change meta that belongs to ACF fields
- Security – Basic uploader nonces are now tied to the content being edited
- Security – The AJAX request that loads field groups while editing a post no longer returns field groups assigned to other content
- Security – The Relationship, Post Object, and Page Link fields no longer reveal the titles or statuses of posts the current user cannot read, and no longer save newly selected posts the user cannot read. Existing selections the user cannot read are shown as “(Restricted item)” and are kept when the user saves. Thanks to vuxvinh via WPScan for the responsible disclosure
- Security – Relationship, Post Object, and Page Link values rendered in ACF Blocks now leave out posts the author of the post cannot read, such as another user’s unpublished drafts. This can be disabled with the new acf/fields/relational/hide_unreadable_posts filter
- Security – Bidirectional fields now only add references to posts the current user can edit, terms they can assign, and users they can edit or set as a post’s author. Saves made with update_field(), WP-CLI, or cron are not checked, and the new acf/bidirectional/can_update_target and acf/is_trusted_save_context filters can adjust this. Thanks to vuxvinh via WPScan for the responsible disclosure
Previous releases
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
6.8.9
- View Release Post
- Enhancement – ACF Blocks registered via acf_register_block_type() or block.json without an explicit version now default to v3 on WordPress 7.1 or later. Blocks that specify a version continue to use the version they declare, and the default can be customized via the acf/blocks/default_block_version filter
- Enhancement – ACF Blocks v3 now supports a renderPreview option in block.json. Setting “renderPreview”: false shows a placeholder with the block’s icon, title, and an “Edit Block” button in the editor instead of rendering the block’s template as a live preview. The block continues to render normally on the front-end, and legacy v2 blocks combining “mode”: “edit” with “supports”: { “mode”: false } are automatically migrated when upgraded to v3
- Fix – Inline editable fields in ACF Blocks V3 no longer require a second click before they can be edited
- Fix – Radio buttons now appear correctly in ACF admin screens