BNC BiblioShare Security & Risk Analysis

wordpress.org/plugins/bnc-biblioshare

Displays a book's cover image, title, author, and other book data from BiblioShare

20 active installs v1.0.9 PHP + WP 2.5.1+ Updated Mar 29, 2019
bookbookslibrarieslibraryreading
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is BNC BiblioShare Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 7yr ago
Risk Assessment

The 'bnc-biblioshare' plugin v1.0.9 exhibits a mixed security posture. On the positive side, it demonstrates good practices regarding SQL queries, exclusively using prepared statements, and has a clean vulnerability history with no known CVEs. It also includes nonce and capability checks, indicating some awareness of security fundamentals.

However, significant concerns arise from the static analysis. The presence of an unprotected AJAX handler represents a direct attack vector. Furthermore, the complete lack of output escaping across all identified outputs is a critical flaw, potentially leading to cross-site scripting (XSS) vulnerabilities when user-supplied data is displayed without proper sanitization. The taint analysis, while limited in scope, did reveal a flow with unsanitized paths, further reinforcing the XSS risk.

While the absence of historical vulnerabilities is encouraging, it does not negate the immediate risks identified in the current version. The combination of an unprotected entry point and widespread output escaping deficiencies creates a substantial risk of exploitation, primarily through XSS attacks. Addressing the output escaping issue and securing the AJAX handler should be immediate priorities.

Key Concerns

  • AJAX handler without auth checks
  • All outputs are unescaped
  • Flows with unsanitized paths
Vulnerabilities
None known

BNC BiblioShare Security Vulnerabilities

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

BNC BiblioShare Code Analysis

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

Output Escaping

0% escaped15 total outputs
Data Flows
1 unsanitized

Data Flow Analysis

1 flows1 with unsanitized paths
<booknet_options> (booknet_options.php:0)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface
1 unprotected

BNC BiblioShare Attack Surface

Entry Points2
Unprotected1

AJAX Handlers 1

authwp_ajax_my_special_actionbooknet.php:339

Shortcodes 1

[booknet] booknet.php:41
WordPress Hooks 5
actionadmin_initbooknet.php:39
actionadmin_menubooknet.php:40
filterwidget_textbooknet.php:42
filtermce_buttonsbooknet.php:49
filtermce_external_pluginsbooknet.php:50
Maintenance & Trust

BNC BiblioShare Maintenance & Trust

Maintenance Signals

WordPress version tested4.1.42
Last updatedMar 29, 2019
PHP min version
Downloads6K

Community Trust

Rating0/100
Number of ratings0
Active installs20
Developer Profile

BNC BiblioShare Developer Profile

John Miedema

1 plugin · 20 total installs

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

How We Detect BNC BiblioShare

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/bnc-biblioshare/libraries/booknet_button.js
Script Paths
/wp-content/plugins/bnc-biblioshare/libraries/booknet_button.js

HTML / DOM Fingerprints

Shortcode Output
[booknetbooknet_insertbookdata
FAQ

Frequently Asked Questions about BNC BiblioShare