Hijri Calendar Widget Security & Risk Analysis

wordpress.org/plugins/hijri-calendar-widget

Wordpress plugin for historically accurate Hijri conversions.

10 active installs v1.0.0 PHP + WP 3.0.1+ Updated Sep 8, 2015
calendarconversiondatehijriwidget
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Hijri Calendar Widget Safe to Use in 2026?

Generally Safe

Score 85/100

Hijri Calendar Widget has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 10yr ago
Risk Assessment

The "hijri-calendar-widget" v1.0.0 plugin exhibits a generally good security posture based on the provided static analysis. The absence of any known CVEs and the clean vulnerability history suggest a well-maintained or less targeted plugin. The code analysis reveals a lack of dangerous functions, a complete absence of direct SQL queries (all use prepared statements), and no file operations or external HTTP requests, which are all positive indicators. Taint analysis also shows no critical or high-severity issues, further reinforcing a low-risk profile.

However, there are areas for improvement that introduce potential risks. The most significant concern is the low percentage of properly escaped output (27%). This indicates a substantial risk of Cross-Site Scripting (XSS) vulnerabilities, especially if user-supplied data is not adequately sanitized before being displayed. Furthermore, the complete absence of nonce checks and capability checks across all identified entry points (though there are none in this specific scan) would be a critical concern if any such entry points were discovered. While the current scan reports zero entry points, this could be an oversight or a feature of this specific version. A higher output escaping rate is crucial to mitigate XSS risks.

In conclusion, while the plugin has a strong foundation with no known vulnerabilities and good practices in areas like SQL handling, the high number of unescaped outputs presents a notable weakness. The lack of any identified entry points is positive but should be continuously monitored. Addressing the output escaping is the most pressing security enhancement needed for this plugin to further reduce its risk profile.

Key Concerns

  • Low output escaping rate (27%)
Vulnerabilities
None known

Hijri Calendar Widget Security Vulnerabilities

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

Hijri Calendar Widget Code Analysis

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

Output Escaping

27% escaped15 total outputs
Attack Surface

Hijri Calendar Widget Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 2
actionwp_enqueue_scriptshijri-calendar-widget.php:27
actionwidgets_inithijri-calendar-widget.php:40
Maintenance & Trust

Hijri Calendar Widget Maintenance & Trust

Maintenance Signals

WordPress version tested3.4.2
Last updatedSep 8, 2015
PHP min version
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Hijri Calendar Widget Developer Profile

bftech

1 plugin · 10 total installs

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

How We Detect Hijri Calendar Widget

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/hijri-calendar-widget/js/script.js
Script Paths
/wp-content/plugins/hijri-calendar-widget/js/script.js
Version Parameters
hijri-calendar-widget/js/script.js?ver=1.0.0

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Hijri Calendar Widget