Plugin info

Total downloads: 219,580
Active installs: 50,000
Total reviews: 56
Average rating: 4.8
Support threads opened: 7
Support threads resolved: 2 (29%)
Available in: 14 language(s)
Contributors: 2
Last updated: 12/3/2025 (28 days ago)
Added to WordPress: 11/21/2024 (1 years old)
Minimum WordPress version: 6.2
Tested up to WordPress version: 6.9
Minimum PHP version: 7.4

Maintenance & Compatibility

Maintenance score

Actively maintained • Last updated 28 days ago • Support resolved 29% • 56 reviews

70/100

Is Secure Custom Fields abandoned?

Likely maintained (last update 28 days ago).

Compatibility

Requires WordPress: 6.2
Tested up to: 6.9
Requires PHP: 7.4

Similar & Alternatives

Explore plugins with similar tags, and compare key metrics like downloads, ratings, updates, support, and WP/PHP compatibility.

Advanced Custom Fields (ACF®)
Rating 4.5/5 (1,420 reviews)Active installs 2,000,000
Table Field Add-on for ACF and SCF
Rating 4.9/5 (59 reviews)Active installs 60,000
Really Simple CSV Importer
Rating 4.9/5 (107 reviews)Active installs 40,000
Fields ACF & SCF for Elementor and Divi
Rating 0.0/5 (0 reviews)Active installs 10
Better Field Groups for ACF
Rating 0.0/5 (0 reviews)Active installs 0

Description

Secure Custom Fields (SCF) extends WordPress’s capabilities, transforming it into a flexible content management tool. With SCF, managing custom data becomes straightforward and efficient.

Easily create fields on demand.
The SCF builder makes it easy to add fields to WordPress edit screens, whether you’re adding a new “ingredients” field to a recipe or designing complex metadata for a specialized site.

Flexibility in placement.
Fields can be applied throughout WordPress—posts, pages, users, taxonomy terms, media, comments, and even custom options pages—organizing your data how you want.

Display seamlessly.
Using SCF functions, you can display custom field data in your templates, making content integration easy for all levels of developers.

A comprehensive content management solution.
Beyond custom fields, SCF allows you to register new post types and taxonomies directly from the SCF interface, providing more control without needing additional plugins or custom code.

Accessible and user-friendly design.
The field interface aligns with WordPress’s native design, creating an experience that’s both accessible and easy for content creators to use.

Installing this plugin will deactivate plugins with matching function names/functionality, specifically Advanced Custom Fields, Advanced Custom Fields Pro, and the legacy Secure Custom Fields plugins, to avoid code errors (this is the same behavior as ACF Pro).

Read more about Secure Custom Fields at developer.wordpress.org/secure-custom-fields.

Features

  • Clear and easy-to-use setup
  • Robust functions for content management
  • Over 30 Field Types

Installation

No installation instructions available

Frequently Asked Questions

No FAQ available

Review feed

squarecandy
11/26/2024

Unprecedented bad behavior

In case anyone is not clear - this is a "nulled" plugin - an exact copy of the paid support Pro version of Advanced Custom Fields, with the code to handle licensing and updates stripped out. This clearly part of the petty high school drama playing out between two multi million dollar for-profit companies, and it is going to wreak havoc on the entire WordPress ecosystem. Who's going to invest in creating great Pro plugins if everyone's always afraid that Wordpress.org itself is going to just rip them and put them up on the main plugin repo if they don't like you today. The "freemium" model has created great jobs for a lot of small development shops and many individual designers and developers depend on the quality and support you get from paid Pro level plugins to do their jobs. I have no particular love for WP Engine, but this sets a horrible new precedent that is going to put the livelihoods of may less powerful individuals at risk. It must be stopped now!
Pexle Chris
11/27/2024

Unacceptable behaviour

Hello, WordPress contributors, I am using WordPress as a developer more than 5 years. And I have also contributed. There are some plugins in the Repository WP Adminer, Library Viewer, Gift Wrapping for WooCommerce, with old these plugins have 100% 5-stars reviews. But this behaviour is Unacceptable. What are the GPL requirements? Here you just took Advanced Custom Field Pro, removed their license system, changed the plugin author details without copyright anywhere WP Engine (the author of ACF Pro) and you released it as yours. Such other "marketplaces" do in the Web... Is all this ethical? I have also paid plugins! Are you going to take them also? Trust in WordPress is being cloned with your actions...
fotkin
1/19/2025

Great replacement for ACF

ACF disabled gallery field and broke few sites, changed to SCF and everything started to work again. Thank you!
Astral Internet
1/23/2025

Work great, no add for premium

I am pleased to observe the addition of numerous valuable features without the frequent reminders about upgrading to a premium version.

Screenshots

  1. Add groups of custom fields.

    Add groups of custom fields.

  2. Easy to add custom content while writing.

    Easy to add custom content while writing.

  3. Need a new post type? Just add it!

    Need a new post type? Just add it!

  4. Navigate the various field types with ease.

    Navigate the various field types with ease.

Changelog

6.7.0

Release Date 2 Dec 2025

Features

  • Tested compatibility up to WordPress 6.9.
  • Abilities support. Taxonomy abilities.
  • JSON schemas. Taxonomy schema.

6.6.0

Release Date 19 Nov 2025

Features

  • Backported features up to 6.6.0.
  • Abilities API integration. Post Type abilities.
  • JSON schemas validation infrastructure.

Fixes

  • Fixed Function in network.php
  • SCF label in “More” menu.
  • Get the formatted_value from the original field value.
  • Blocks V3: Fix flexible content not working in sidebar – modal.
  • Use specific entity prefixes for key generation when duplicating entities.

6.5.7

Release Date 28 Aug 2025

Features

  • Flexible Content layouts can now be renamed in the post editor, giving content editors better clarity when managing layouts.
  • Flexible Content layouts can now be disabled, preventing them from rendering on the frontend without needing to delete their data.
  • Flexible Content layouts can now be collapsed and expanded in bulk for faster content editing.
  • Editing a Flexible Content layout now highlights the layout being edited, making it easier to identify.
  • The Date and Date Time Picker fields can now be configured to default to the current date.
  • Custom Icon Picker tabs now work correctly when used inside an ACF Block.
  • Duplicating a Field Group no longer causes a fatal error when using Russian translations.
  • ACF classes no longer use dynamic class properties, improving compatibility with PHP 8.2+.
  • Field group metabox collapse and expand buttons are no longer misaligned in the post editor.
  • HTML is now escaped from field validation errors and tooltips.
  • Added a new source parameter to the /wp/v2/types REST API endpoint that allows filtering post types by their origin: core (WordPress built-in), scf (for SCF managed types), or other for the rest of CPTs.

Security

– Unsafe HTML in field group labels is now correctly escaped for conditionally loaded field groups, resolving a JS execution vulnerability in the classic editor.
– HTML is now escaped from field group labels when output in the ACF admin.
– Bidirectional and Conditional Logic Select2 elements no longer render HTML in field labels or post titles.
– The acf.escHtml function now uses the third party DOMPurify library to ensure all unsafe HTML is removed. A new esc_html_dompurify_config JS filter can be used to modify the default behaviour.
– Post titles are now correctly escaped whenever they are output by ACF code. Thanks to Shogo Kumamaru of LAC Co., Ltd. for the responsible disclosure.
– An admin notice is now displayed when version 3 of the Select2 library is used, as it has now been deprecated in favor of version 4.

6.5.6

Release discarded due to SVN errors.

6.5.5

Release Date 31 Jul 2025

Features

  • Connect block attributes with custom fields via UI.
  • Remove the word ‘New’ from default add-new* label values.

Bug Fixes

  • Bug fix: Prevent fatal if class does not exist on Beta Features.

6.5.4

Release Date 30 Jul 2025

Revert from 6.5.2.

6.5.2

Release Date 30 Jul 2025

Features

  • Connect block attributes with custom fields via UI.
  • Remove the word ‘New’ from default add-new* label values.

6.5.1

Release Date 2 Jul 2025

Bug Fixes

  • Command Palette: Use @wordpress\icons instead of Dashicons.

6.5.0

Release Date 23 Jun 2025

Enhancements & Features

  • Added Command Palette support.
  • Added editor preview to acf-field source.
  • Added an endpoint to retrieve the custom fields of a post type.
  • Added nav menu as field type.
  • Added compatibility with Woo HPOS for order fields and subscriptions. ( Ported from ACF )
  • Create new options when editing a fields value on Selector. ( Ported from ACF )
  • The “Escaped HTML” warning notice is now disabled by default. ( Ported from ACF )
  • Added new acf/fields/icon_picker/{tab_name}/icons filter ( Ported from ACF )

Bug Fixes

  • Update initialization of the acfL10n object to ensure it’s available globally.
  • SCF Blocks are now forced into preview mode when editing a synced pattern. ( Ported from ACF )
  • SCF no longer causes an infinite loop in bbPress when editing replies. ( Ported from ACF )
  • Changing a field type no longer enables the “Allow Access to Value in Editor UI” setting. ( Ported from ACF )
  • Blocks registered via acf_register_block_type() with a parent value of null no longer fail to register. ( Ported from ACF )
  • Fix AJAX repeater pagination. ( Ported from ACF )
  • Paginated Repeater fields no longer save duplicate values when saving to a WooCommerce Order with HPOS disabled ( Ported from ACF )

Testing

  • Added an initial batch of e2e tests.

6.4.2

Release Date 14 Apr 2025

  • Resolved issue with shortcode translation not parsing correctly.
  • Improve validation for an URL on field admin.

6.4.1

Release Date 7 Mar 2025

  • Forked from Advanced Custom Fields®
  • Various updates to coding standards.
  • Updated to rely on the WordPress.org translation packs for all strings.

6.3.9

Release Date 22nd October 2024

  • Version update release

6.3.6.3

Release Date 15th October 2024

  • Security – Editing a Field in the Field Group editor can no longer execute a stored XSS vulnerability. Thanks to Duc Luong Tran (janlele91) from Viettel Cyber Security for the responsible disclosure
  • Security – Post Type and Taxonomy metabox callbacks no longer have access to any superglobal values, hardening the original fix from 6.3.6.2 even further
  • Fix – SCF Fields now correctly validate when used in the block editor and attached to the sidebar

6.3.6.2

Release Date 12th October 2024

  • Security – Harden fix in 6.3.6.1 to cover $_REQUEST as well.
  • Fork – Change name of plugin to Secure Custom Fields.

6.3.6.1

Release Date 7th October 2024

  • Security – SCF defined Post Type and Taxonomy metabox callbacks no longer have access to $_POST data. (Thanks to the Automattic Security Team for the disclosure)