BuddyPress Conditional Field Groups Security & Risk Analysis

wordpress.org/plugins/buddypress-conditional-field-groups

Conditionally hide BuddyPress XProfile Field Groups based on user role.

80 active installs v0.1.0 PHP + WP 3.5.1+ Updated May 30, 2015
buddypressxprofile-fields
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is BuddyPress Conditional Field Groups Safe to Use in 2026?

Generally Safe

Score 85/100

BuddyPress Conditional Field Groups has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 10yr ago
Risk Assessment

The overall security posture of the buddypress-conditional-field-groups plugin v0.1.0 appears to be relatively strong due to the lack of identified vulnerabilities and the absence of common risky code patterns like direct SQL queries or external HTTP requests. The presence of a nonce check is also a positive sign. However, the static analysis reveals a significant concern regarding output escaping, with only 17% of outputs being properly escaped. This could potentially lead to Cross-Site Scripting (XSS) vulnerabilities if user-supplied data is not sufficiently sanitized before being displayed.

The plugin exhibits a zero attack surface in terms of AJAX handlers, REST API routes, shortcodes, and cron events, which significantly reduces its exposure to common attack vectors. The absence of dangerous functions and taint analysis results further suggests a clean codebase. The vulnerability history is also clear, with no known CVEs, which is a strong indicator of past security diligence or the plugin's limited exposure. Despite these strengths, the low output escaping percentage remains a notable weakness that warrants attention.

Key Concerns

  • Low output escaping percentage
Vulnerabilities
None known

BuddyPress Conditional Field Groups Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Version History

BuddyPress Conditional Field Groups Release Timeline

No version history available.
Code Analysis
Analyzed Mar 16, 2026

BuddyPress Conditional Field Groups Code Analysis

Dangerous Functions
0
Raw SQL Queries
0
0 prepared
Unescaped Output
5
1 escaped
Nonce Checks
1
Capability Checks
0
File Operations
0
External Requests
0
Bundled Libraries
0

Output Escaping

17% escaped6 total outputs
Attack Surface

BuddyPress Conditional Field Groups Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 4
actioninitbuddypress_conditional_field_groups.php:54
actionadmin_menuincludes\setup.php:34
actionadmin_initincludes\setup.php:35
filterbp_xprofile_get_groupsincludes\setup.php:37
Maintenance & Trust

BuddyPress Conditional Field Groups Maintenance & Trust

Maintenance Signals

WordPress version tested4.2.0
Last updatedMay 30, 2015
PHP min version
Downloads6K

Community Trust

Rating80/100
Number of ratings3
Active installs80
Developer Profile

BuddyPress Conditional Field Groups Developer Profile

Tanner Moushey

3 plugins · 2K total installs

84
trust score
Avg Security Score
85/100
Avg Patch Time
30 days
View full developer profile
Detection Fingerprints

How We Detect BuddyPress Conditional Field Groups

Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.

Asset Fingerprints

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about BuddyPress Conditional Field Groups