BuddyPress to WordPress Full Sync Security & Risk Analysis

wordpress.org/plugins/bp2wp-full-sync

BuddyPress to WordPress Full Sync lets BuddyPress xProfile fields to synchronize with WordPress user fields

200 active installs v0.3.7 PHP + WP 4.0+ Updated Jun 16, 2021
buddypressfieldsprofileusersxprofile
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is BuddyPress to WordPress Full Sync Safe to Use in 2026?

Generally Safe

Score 85/100

BuddyPress to WordPress Full Sync has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 4yr ago
Risk Assessment

The bp2wp-full-sync v0.3.7 plugin exhibits a strong security posture based on the provided static analysis. The absence of any identified AJAX handlers, REST API routes, shortcodes, or cron events with exposed attack surfaces is a significant strength. Furthermore, all SQL queries are properly secured with prepared statements, and there are no file operations or external HTTP requests that could be exploited. The plugin also demonstrates good practice by avoiding bundled libraries and having no recorded vulnerabilities in its history. However, a notable area for improvement is output escaping, with 60% of outputs being properly escaped, leaving 40% potentially vulnerable to cross-site scripting (XSS) attacks if the unescaped data is user-controlled and displayed directly. The lack of nonce checks on the identified capability check is also a minor concern, suggesting a potential for privilege escalation if the capability check is not robust enough on its own and an attacker can trigger the functionality repeatedly without session validation.

Key Concerns

  • Unescaped output detected
  • Missing nonce check for capability check
Vulnerabilities
None known

BuddyPress to WordPress Full Sync Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Code Analysis
Analyzed Mar 17, 2026

BuddyPress to WordPress Full Sync Code Analysis

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

SQL Query Safety

100% prepared4 total queries

Output Escaping

60% escaped5 total outputs
Data Flows
All sanitized

Data Flow Analysis

1 flows
<bp2wp-full-sync> (bp2wp-full-sync.php:0)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

BuddyPress to WordPress Full Sync Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 11
actionwpbp2wp-full-sync.php:93
actionuser_registerbp2wp-full-sync.php:126
filterbp_xprofile_set_field_data_pre_validatebp2wp-full-sync.php:127
actionuser_registerbp2wp-full-sync.php:137
actionpersonal_options_updatebp2wp-full-sync.php:138
actionedit_user_profile_updatebp2wp-full-sync.php:139
filterupdated_user_metabp2wp-full-sync.php:140
actionxprofile_updated_profilebp2wp-full-sync.php:141
actionxprofile_field_after_submitboxbp2wp-full-sync.php:142
actionxprofile_field_after_savebp2wp-full-sync.php:143
actioninitbp2wp-full-sync.php:361
Maintenance & Trust

BuddyPress to WordPress Full Sync Maintenance & Trust

Maintenance Signals

WordPress version tested5.7.15
Last updatedJun 16, 2021
PHP min version
Downloads16K

Community Trust

Rating96/100
Number of ratings12
Active installs200
Developer Profile

BuddyPress to WordPress Full Sync Developer Profile

Sergio De Falco

2 plugins · 1K 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 to WordPress Full Sync

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/bp2wp-full-sync/

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about BuddyPress to WordPress Full Sync