JReferences Security & Risk Analysis

wordpress.org/plugins/jreferences

This plugin adds references and citations functionalities (in a wikipedia-like style).

10 active installs v1.0.3 PHP + WP 4.6+ Updated Jan 2, 2019
citationcommentsfootnotesreference
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is JReferences Safe to Use in 2026?

Generally Safe

Score 85/100

JReferences 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 "jreferences" plugin v1.0.3 exhibits a generally strong security posture based on the provided static analysis. The absence of identified AJAX handlers, REST API routes, shortcodes, or cron events suggests a minimal attack surface, which is further bolstered by the lack of direct file operations or external HTTP requests. The use of prepared statements for all SQL queries is a significant positive indicator, preventing common SQL injection vulnerabilities. However, the static analysis does reveal some areas for improvement. With 6 total outputs, a 33% rate of unescaped output presents a potential cross-site scripting (XSS) risk, as user-supplied data might be rendered directly in the browser without proper sanitization. Furthermore, the complete lack of nonce checks and capability checks across all identified entry points (even though there are none explicitly listed) is a concern. While the current attack surface is zero, any future additions of entry points without these fundamental security mechanisms would immediately expose the plugin to vulnerabilities like Cross-Site Request Forgery (CSRF) and privilege escalation.

Key Concerns

  • Unescaped output detected
  • Missing nonce checks
  • Missing capability checks
Vulnerabilities
None known

JReferences Security Vulnerabilities

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

JReferences Release Timeline

v1.0.3Current
v1.0.2
v1.0
v0.99
v0.98
v0.97
v0.96
v0.95
v0.94
v0.92
v0.91
v0.9a
Code Analysis
Analyzed Apr 16, 2026

JReferences Code Analysis

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

Output Escaping

67% escaped6 total outputs
Attack Surface

JReferences Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 4
actionadmin_menuclass.jref-admin.php:34
actionadmin_initclass.jref-admin.php:35
actionwp_enqueue_scriptsclass.jref-citation.php:185
filterthe_contentclass.jref-citation.php:193
Maintenance & Trust

JReferences Maintenance & Trust

Maintenance Signals

WordPress version tested5.0.25
Last updatedJan 2, 2019
PHP min version
Downloads2K

Community Trust

Rating100/100
Number of ratings2
Active installs10
Developer Profile

JReferences Developer Profile

janiko

5 plugins · 130 total installs

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

How We Detect JReferences

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/jreferences/css/plugin.css

HTML / DOM Fingerprints

CSS Classes
footer_references
Data Attributes
id="note-id='note-id='div_jref_footer'id='references-head'
Shortcode Output
<sup style='font-size:8px;vertical-align:super' id='note-'>[
FAQ

Frequently Asked Questions about JReferences