BibleUp Security & Risk Analysis

wordpress.org/plugins/bibleup

BibleUp transforms Bible references on a webpage into links and makes the text accessible via a flexible and highly-customizable popover.

70 active installs v1.1.0 PHP 7.0+ WP 5.6+ Updated Oct 24, 2024
biblechristianreferencesreftaggingscripture
92
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is BibleUp Safe to Use in 2026?

Generally Safe

Score 92/100

BibleUp 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 "bibleup" plugin version 1.1.0 demonstrates a generally strong security posture based on the provided static analysis. The plugin effectively utilizes prepared statements for all SQL queries, has no file operations, and makes no external HTTP requests, significantly reducing common attack vectors. The presence of nonce checks on both AJAX handlers and a capability check further indicates an effort to secure its entry points. The absence of any recorded vulnerabilities in its history is also a positive sign.

However, there are some areas for improvement. While the plugin has a small attack surface with only two AJAX handlers, and these appear to have some form of authentication, the analysis doesn't explicitly confirm that *all* potential entry points are fully protected against unauthorized access or that all output is sanitized. Approximately 21% of output is not properly escaped, which could lead to cross-site scripting (XSS) vulnerabilities if the unescaped output contains user-supplied data.

In conclusion, "bibleup" v1.1.0 is a relatively secure plugin with good fundamental security practices. The lack of historical vulnerabilities and the use of prepared statements are commendable. The primary concern lies with the unescaped output, which warrants attention to prevent potential XSS issues. Addressing this would further enhance its overall security.

Key Concerns

  • Unescaped output found
Vulnerabilities
None known

BibleUp Security Vulnerabilities

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

BibleUp Code Analysis

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

Output Escaping

79% escaped181 total outputs
Attack Surface

BibleUp Attack Surface

Entry Points2
Unprotected0

AJAX Handlers 2

authwp_ajax_wpsf_export_settingswp-settings-framework\wp-settings-framework.php:126
authwp_ajax_wpsf_import_settingswp-settings-framework\wp-settings-framework.php:127
WordPress Hooks 6
actionadmin_menubibleup.php:36
actionwp_enqueue_scriptsbibleup.php:70
filterwpsf_register_settings_bibleupsettings\settings-general.php:23
actionadmin_initwp-settings-framework\wp-settings-framework.php:109
actionadmin_noticeswp-settings-framework\wp-settings-framework.php:114
actionadmin_enqueue_scriptswp-settings-framework\wp-settings-framework.php:116
Maintenance & Trust

BibleUp Maintenance & Trust

Maintenance Signals

WordPress version tested6.6.5
Last updatedOct 24, 2024
PHP min version7.0
Downloads2K

Community Trust

Rating100/100
Number of ratings2
Active installs70
Developer Profile

BibleUp Developer Profile

BibleUp

1 plugin · 70 total installs

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

How We Detect BibleUp

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/bibleup/wp-settings-framework/css/wpsf.css/wp-content/plugins/bibleup/wp-settings-framework/js/wpsf.js
Script Paths
https://cdn.jsdelivr.net/npm/@bibleup/bibleup@1/dist/umd/bibleup-core.min.js
Version Parameters
bibleup-core?ver=bibleup-style?ver=

HTML / DOM Fingerprints

CSS Classes
bibleup-container
Data Attributes
data-bibleup-container
JS Globals
BibleUp
FAQ

Frequently Asked Questions about BibleUp