Skip to content
PluginCanary

Display custom fields in the frontend

Display custom fields in the frontend - Post and User Profile Fields
by Jose Vega · 500+ active installs · Checked 3 Nov 2026
Healthy

Healthy: maintained, last release 22 Aug 2026, no unpatched vulnerabilities.

96/ 100 Canary Score
Sub-scores for Display custom fields in the frontend
Ownership100
Maintenance100
Security90
SupportNo data
ReputationNo data

How the score works

Quick answers

Is Display custom fields in the frontend still maintained?
Yes. Last release 22 Aug 2026, 0 releases in the last 24 months. 22 Aug 2026 · wordpress.org
Who owns Display custom fields in the frontend, and has it changed hands?
No change recorded. Main committer JoseVega since Jul 2017. 3 Nov 2026 · SVN log
Was Display custom fields in the frontend removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
Is Display custom fields in the frontend safe?
4 known vulnerabilities, all fixed (latest in 1.3.0). Not on the exploited list. 16 Jan 2024 · Wordfence Intelligence
Is the latest Display custom fields in the frontend update safe to install?
No ownership change before 1.3.0. No one-star spike after it. 12 Jan 2024 · Release history

Active signals

Facts we detected, with links to the source.

No open risk signals. Signals appear here when we detect an ownership change, closure, vulnerability or decline.

Ownership timeline

Who commits to the plugin's code on wordpress.org, over time.

Committers and their active periods
JoseVega24 Jul 2017 to 22 Aug 2026, 23 commits

1 committer recorded. No ownership change since 2017.

Maintenance

Last release
2 months ago
Releases, 24 months
0
Tested up to
7.1 current
Requires PHP
not stated supported 8.2+
Releases per quarter
Releases per quarter for Display custom fields in the frontend
Q1 20241
Q2 20240
Q3 20240
Q4 20240
Q1 20250
Q2 20250
Q3 20250
Q4 20250
Q1 20260
Q2 20260
Q3 20260
Q4 20260

Last release 22 Aug 2026. Tested with WordPress 7.1 (current).

Reputation

Last 90 days: no reviews. Lifetime: 5.0.

Rating distribution
5 star8
4 star0
3 star0
2 star0
1 star0

Security record

4 vulnerabilities on record, all patched (latest fixed in 1.3.0).

Show 4 patched vulnerabilities

Sources: Wordfence Intelligence, CISA Known Exploited Vulnerabilities, readme changelogs.

Support

Support history appears after our first snapshots of the forum counts.

Momentum

500+ active installs. History builds with each weekly snapshot.

Momentum history builds with each snapshot.

Healthier alternatives

Same job, rated Healthy, higher Canary Score and at least 10,000 installs. Never sponsored.

No healthier plugin in the same category yet.

Facts

Version1.3.0
AuthorJose Vega
Added24 Jul 2017
Last updated22 Aug 2026
Active installs500+
Requires WordPress4.1
Tested up to7.1.4
Requires PHPnot stated
CategoryContent Management > Blog & Article Publishing
Tagsacf, custom pages, custom fields, wp page templates, wordpress templates

Other plugins by this author: Bulk Edit Products for WooCommerce - WP Sheet Editor, Bulk Edit Posts and Products in Spreadsheet, Bulk Edit Categories and Tags - Create Thousands Quickly on the Editor, WP Required Taxonomies - Categories and Tags Mandatory, Bulk Edit and Create User Profiles - WP Sheet Editor, Bulk Edit YOAST SEO fields in Spreadsheet, Disable Payment Methods based on cart conditions for WooCommerce, Bulk Edit Coupons for WooCommerce - WP Sheet Editor, WP Frontend Admin - Display WP Admin Pages in the Frontend, WP Page Templates, Restrict Products by Country & Country Catalogs for WooCommerce, Hide Header on Posts for Landing Pages

Questions

Is Display custom fields in the frontend still maintained?

Yes. Last release 22 Aug 2026, 0 releases in the last 24 months.

Who owns Display custom fields in the frontend, and has it changed hands?

No change recorded. Main committer JoseVega since Jul 2017.

Was Display custom fields in the frontend removed from wordpress.org?

No. Listed on wordpress.org as of 3 Nov 2026.

Is Display custom fields in the frontend safe?

4 known vulnerabilities, all fixed (latest in 1.3.0). Not on the exploited list.

Is the latest Display custom fields in the frontend update safe to install?

No ownership change before 1.3.0. No one-star spike after it.

Data: wordpress.org Plugins API, plugins SVN and Trac, wordpress.org reviews and support forum, Wordfence Intelligence, CISA KEV, NVD.Plugin data refreshed 3 Nov 2026.Report a data issue