Users to CRM Contacts Security & Risk Analysis

wordpress.org/plugins/users-to-crm-contacts

Integrate WordPress with SugarCRM/SuiteCRM to sync user data, simplify lead management, and improve user tracking

10 active installs v1.6 PHP 7.4+ WP 5.6+ Updated Dec 15, 2024
synchronize-wp-users-with-sugarcrm-suitecrmsynchronize-wp-users-with-suitecrmwordpress-users-to-crm-contactswordpress-with-crmwp-users
92
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Users to CRM Contacts Safe to Use in 2026?

Generally Safe

Score 92/100

Users to CRM Contacts has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 1yr ago
Risk Assessment

The "users-to-crm-contacts" plugin v1.6 exhibits a mixed security posture. On the positive side, it demonstrates strong adherence to secure coding practices regarding SQL queries and output escaping, with 100% of both using prepared statements and proper escaping respectively. The absence of any historical vulnerabilities, critical or otherwise, suggests a history of relatively secure development. However, a significant concern arises from the substantial attack surface, specifically the seven unprotected AJAX handlers, which represent a direct pathway for potential exploitation if not properly secured by other means not evident in this analysis. The taint analysis further highlights this by revealing seven high-severity flows with unsanitized paths, strongly correlated with these unprotected AJAX endpoints.

The lack of reported CVEs is encouraging, but the presence of high-severity taint flows alongside unprotected AJAX handlers indicates a clear and present risk. While the plugin avoids common pitfalls like raw SQL queries or unescaped output, the vulnerability in its authentication and sanitization of AJAX endpoints, as evidenced by the taint analysis, is a critical weakness. The plugin's strengths in SQL and output handling are undermined by its weaknesses in securing its primary entry points. Therefore, while the historical record is clean, the current code analysis points to a medium to high risk due to the exploitable attack surface.

Key Concerns

  • Unprotected AJAX handlers
  • High severity unsanitized taint flows
  • External HTTP requests (potential for SSRF)
Vulnerabilities
None known

Users to CRM Contacts Security Vulnerabilities

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

Users to CRM Contacts Code Analysis

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

SQL Query Safety

100% prepared19 total queries

Output Escaping

100% escaped60 total outputs
Data Flows
7 unsanitized

Data Flow Analysis

12 flows7 with unsanitized paths
oepl_wp_user_to_crm_extra_profile_fields (OEPL_UserToCRM.conf.php:101)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface
7 unprotected

Users to CRM Contacts Attack Surface

Entry Points8
Unprotected7

AJAX Handlers 8

authwp_ajax_wpuser_to_crm_test_and_save_credentialsWPUserToCRM_admin_functions.php:76
authwp_ajax_wpuser_to_crm_contacts_field_syncWPUserToCRM_admin_functions.php:122
authwp_ajax_wpuser_to_crm_update_contact_grid_statusWPUserToCRM_admin_functions.php:376
authwp_ajax_wpuser_to_crm_save_custom_metaWPUserToCRM_admin_functions.php:408
authwp_ajax_wpuser_to_crm_save_contact_to_crm_moduleWPUserToCRM_admin_functions.php:439
authwp_ajax_wpuser_to_crm_create_new_contactWPUserToCRM_admin_functions.php:480
authwp_ajax_wpuser_to_crm_update_existing_contactWPUserToCRM_admin_functions.php:540
authwp_ajax_wpuser_to_crm_save_user_to_contactsWPUserToCRM_admin_functions.php:783
WordPress Hooks 7
actionadmin_noticesOEPL_UserToCRM.conf.php:29
actionuser_registerOEPL_UserToCRM.conf.php:31
actionadmin_menuOEPL_UserToCRM.conf.php:49
actionshow_user_profileOEPL_UserToCRM.conf.php:99
actionedit_user_profileOEPL_UserToCRM.conf.php:100
actionadmin_footerOEPL_UserToCRM.conf.php:104
actionadmin_footerOEPL_UserToCRM.conf.php:194
Maintenance & Trust

Users to CRM Contacts Maintenance & Trust

Maintenance Signals

WordPress version tested6.7.5
Last updatedDec 15, 2024
PHP min version7.4
Downloads3K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Alternatives

Users to CRM Contacts Alternatives

No alternatives data available yet.

Developer Profile

Users to CRM Contacts Developer Profile

Dipesh Patel

2 plugins · 110 total installs

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

How We Detect Users to CRM Contacts

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/users-to-crm-contacts/style/style.css/wp-content/plugins/users-to-crm-contacts/js/sweetalert2.min.js/wp-content/plugins/users-to-crm-contacts/js/OEPL_users.js
Script Paths
/wp-content/plugins/users-to-crm-contacts/js/sweetalert2.min.js/wp-content/plugins/users-to-crm-contacts/js/OEPL_users.js
Version Parameters
users-to-crm-contacts/style.css?ver=1.0.0users-to-crm-contacts/js/sweetalert2.min.js?ver=1.0.0users-to-crm-contacts/js/OEPL_users.js?ver=1.0.0

HTML / DOM Fingerprints

CSS Classes
submit_to_crmdialog1dialog2oe-loader-sectionoe-loading-section-titleoe-loader-icon
Data Attributes
id="Update_to_CRM"name="Update_to_CRM"id="Submit_to_CRM"name="Submit_to_CRM"
JS Globals
objusertocrm
FAQ

Frequently Asked Questions about Users to CRM Contacts