bSecure for GiveWP Security & Risk Analysis

wordpress.org/plugins/bsecure-give

bSecure for GiveWP

0 active installs v1.0.0 PHP + WP 4.7+ Updated Jun 21, 2023
checkoutpaymentsecure
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is bSecure for GiveWP Safe to Use in 2026?

Generally Safe

Score 85/100

bSecure for GiveWP has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 2yr ago
Risk Assessment

The bsecure-give plugin version 1.0.0 exhibits a generally strong security posture based on the provided static analysis. The absence of identified dangerous functions, SQL injection vulnerabilities, file operations, external HTTP requests, and the use of prepared statements for all SQL queries are all positive indicators. Furthermore, the plugin has no recorded vulnerability history, suggesting a diligent approach to security over time. However, a significant concern lies in the complete lack of nonce checks and capability checks. This, coupled with the absence of any identified AJAX handlers, REST API routes, or shortcodes, raises questions about how user interaction and data handling are secured, especially if functionality is added in future versions that might introduce such entry points. While the current version appears clean, the lack of fundamental security mechanisms for potential future interactions presents a latent risk.

Key Concerns

  • Missing nonce checks
  • Missing capability checks
  • 76% output escaping, not 100%
Vulnerabilities
None known

bSecure for GiveWP Security Vulnerabilities

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

bSecure for GiveWP Release Timeline

v1.0.0Current
Code Analysis
Analyzed Mar 17, 2026

bSecure for GiveWP Code Analysis

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

Output Escaping

76% escaped33 total outputs
Attack Surface

bSecure for GiveWP Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 13
actionplugins_loadedbsecure-give.php:24
actiongive_bsecure_cc_formbsecure-give.php:37
filtergive_payment_gatewaysbsecure-give.php:63
filtergive_get_sections_gatewaysbsecure-give.php:85
filtergive_get_settings_gatewaysbsecure-give.php:169
actiongive_gateway_bsecurebsecure-give.php:311
actiongive_donation_form_user_infobsecure-give.php:313
filtergive_update_donor_informationbsecure-give.php:507
actiongive_insert_paymentbsecure-give.php:516
actiongive_payment_view_detailsbsecure-give.php:569
actionwp_loadedincludes\class-bsecure-give.php:67
actionwp_enqueue_scriptsincludes\class-bsecure-give.php:76
actionadmin_enqueue_scriptsincludes\class-bsecure-give.php:78
Maintenance & Trust

bSecure for GiveWP Maintenance & Trust

Maintenance Signals

WordPress version tested6.2.9
Last updatedJun 21, 2023
PHP min version
Downloads3K

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

bSecure for GiveWP Developer Profile

BSecure - Your Universal Checkout

2 plugins · 70 total installs

63
trust score
Avg Security Score
77/100
Avg Patch Time
297 days
View full developer profile
Detection Fingerprints

How We Detect bSecure for GiveWP

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/bsecure-give/assets/css/bsecure-give-main.css/wp-content/plugins/bsecure-give/assets/js/bsecure-give-main.js
Version Parameters
bsecure-give/assets/css/bsecure-give-main.css?ver=bsecure-give/assets/js/bsecure-give-main.js?ver=

HTML / DOM Fingerprints

CSS Classes
bsecure-give-settings
HTML Comments
Save Live Credentials Startchange the insta_for_give prefix to avoid collisions with other functions.
Data Attributes
data-give-id
JS Globals
give_bsecure_give_options
FAQ

Frequently Asked Questions about bSecure for GiveWP