Skip to content
PluginCanary
Limited data: this plugin has under 1,000 active installs and less than 12 weeks of history with us, so we show signals but no status band yet.

WP Frontend Profile

by Glowlogix · 100+ active installs · Checked 3 Nov 2026
Limited data1 Critical1 Warning

Limited data: WP Frontend Profile has under 1,000 active installs and less than 12 weeks of history, so we do not rate it yet.

39/ 100 Canary Score

Capped at 39: a vulnerability has no patch.

Sub-scores for WP Frontend Profile
Ownership100
Maintenance50
Security30
Support70
Reputation70

How the score works

Quick answers

Is WP Frontend Profile still maintained?
Yes. Last release 21 Feb 2026, 1 release in the last 24 months. 21 Feb 2026 · wordpress.org
Who owns WP Frontend Profile, and has it changed hands?
No change recorded. Main committer glowlogix since Aug 2019. 3 Nov 2026 · SVN log
Was WP Frontend Profile removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
Is WP Frontend Profile safe?
No. 1 known vulnerability has no fix in the current version. 6 Mar 2026 · Wordfence Intelligence
Is the latest WP Frontend Profile update safe to install?
No ownership change before 1.3.9. No one-star spike after it. 21 Feb 2026 · Release history

Active signals

Facts we detected, with links to the source.

  • CriticalSEC-2Vulnerability published 23 Feb 2026 still has no fix after 14 days. Disable or replace the plugin. No fix has been released.9 Mar 2026Evidence
  • WarningMNT-2Tested up to WordPress 6.8.12, 3 major versions behind 7.1.4. Plan a replacement if the plugin is important to your site.3 Nov 2026Evidence

Ownership timeline

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

Committers and their active periods
wpmarkuk6 Dec 2014 to 2 Dec 2018, 8 commits
glowlogix5 Aug 2019 to 21 Feb 2026, 27 commits

2 committers recorded. No ownership change since 2014.

Maintenance

Last release
9 months ago
Releases, 24 months
1
Tested up to
6.8 vs 7.1
Requires PHP
5.2.17 supported 8.2+
Releases per quarter
Releases per quarter for WP Frontend Profile
Q1 20243
Q2 20242
Q3 20243
Q4 20240
Q1 20250
Q2 20250
Q3 20250
Q4 20250
Q1 20261
Q2 20260
Q3 20260
Q4 20260

Last release 21 Feb 2026. Tested up to 6.8, 3 major versions behind WordPress 7.1.

Reputation

Last 90 days: no reviews. Lifetime: 4.3.

Rating distribution
5 star6
4 star1
3 star1
2 star1
1 star0

Security record

2 vulnerabilities in 24 months (8 on record), 1 with no fix in the current version.

PublishedIssueCVSSAffectedFixed inDays to patch
23 Feb 2026Frontend Profile <= 1.3.9 - Missing Authorization5.3<= 1.3.9No fixn/a
Show 7 patched vulnerabilities

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

Support

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

Momentum

100+ 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.9
AuthorGlowlogix
Added6 Dec 2014
Last updated21 Feb 2026
Active installs100+
Requires WordPress4.0.1
Tested up to6.8.12
Requires PHP5.2.17
Categorynot stated
Tagslogin, users, profile, register, user meta

Questions

Is WP Frontend Profile still maintained?

Yes. Last release 21 Feb 2026, 1 release in the last 24 months.

Who owns WP Frontend Profile, and has it changed hands?

No change recorded. Main committer glowlogix since Aug 2019.

Was WP Frontend Profile removed from wordpress.org?

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

Is WP Frontend Profile safe?

No. 1 known vulnerability has no fix in the current version.

Is the latest WP Frontend Profile update safe to install?

No ownership change before 1.3.9. 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