Secure Custom Fields

How well this listing is tuned to rank in WordPress.org search, on the factors an owner controls. Not popularity, optimization.

Directory rank vs rivals

wp.org popularity rank over time · higher is better · when a rival's line climbs above yours, they've overtaken you

How often this plugin actually ships. A steady rhythm is the maintenance signal a single "last updated" date can't show.

Share of active installs on each version of this plugin · 38% run the current release. Green is the current release; a big slice on older versions is a user base that has stopped updating.

Refined from the date this plugin crossed into its current band.

At the current install trend, crossing 100K+ in roughly 62 days.

No paid tier is visible, so we don't put a figure on revenue or sale value: that would be guessing. The install base is a real asset to an acquirer, just not one public data lets us price.

Recent releases and news for this plugin

1. — Version 6.9.2 Release Date 21st July 2026 Fixes Fixed Google Maps field values being double-encoded when saved inside a block. Inserting a Link field value in the Classic Editor no longer triggers validation for other required fields 6.9.2
2. — Version 6.9.1 Release Date 2nd July 2026 Security Capped the number of user-contributed choices that can be persisted to checkbox, radio, and select field definitions at 1000 by default, with a new acf/fields/max_appended_choices filt 6.9.1
3. — Version 6.9.0 Release Date 23rd June 2026 Hardening Improved input validation when duplicating field groups, post types, and taxonomies, including ownership and type checks on the target. Restricted persistence of custom choices on ch 6.9.0
4. — Version 6.8.9 Release Date 15th June 2026 Security Hardened the escaping of wp_options LIKE queries used when loading option-page meta and during taxonomy term cleanup, switching to esc_like() so option-name prefixes are always matche 6.8.9
5. — Version 6.8.8 Release Date 11th June 2026 Security AJAX field handlers now validate that the request nonce was created for the expected field type, so a nonce minted for one field type can no longer be replayed against another field t 6.8.8
6. — Version 6.8.7 Release Date 8th June 2026 Fixes SCF’s Abilities API integration for its internal post types no longer triggers PHP warnings, notices, or a fatal error (500) on block editor and REST API requests when another active plug 6.8.7

Automated install-time checks, tested on PHP 8.1.12 · WP 7.0

Translated into 36 languages, 9 at 90% or more

Plus 12 more locales with partial translations.

Growth timeline

Install-tier crossings we have observed, and how long each tier took to outgrow

1. 2026-08-05 80K+ → 90K+ up after 62 days in tier
2. 2026-06-04 70K+ → 80K+ up after 68 days in tier
3. 2026-03-28 60K+ → 70K+ up after 62 days in tier
4. 2026-01-25 50K+ → 60K+ up after 66 days in tier
5. 2025-11-20 40K+ → 50K+ up after 60 days in tier
6. 2025-09-21 30K+ → 40K+ up after 68 days in tier
7. 2025-07-15 20K+ → 30K+ up after 67 days in tier
8. 2025-05-09 10K+ → 20K+ up after 68 days in tier

Competes with

The plugins that solve the same job, ranked by shared tags then reach, closest match first. The letter on the right is each plugin's health grade (A best, F worst).

• Advanced Custom Fields (ACF®) 2M+ installs · 4.5★ · 3 shared tags A
• Advanced Custom Fields: Extended 100K+ installs · 4.7★ · 3 shared tags B
• Custom Field Template 30K+ installs · 4.0★ · 3 shared tags B
• ACF: Fields in Custom Table 80+ installs · 4.1★ · 3 shared tags D
• Custom Block Builder – Lazy Blocks 20K+ installs · 4.8★ · 2 shared tags A
• Product Input Fields for WooCommerce 4K+ installs · 4.0★ · 2 shared tags B

Embed this report card

Drop a live Pulse card for Secure Custom Fields into a readme, a review or a deck. It updates itself.

Secure Custom Fields: 90K+ active installs, 4.8★ (64 reviews). Plugin Pulse (WP Mayor), as of 2026-08-25. https://plugins.wpmayor.com/plugin/secure-custom-fields