Hijri Security & Risk Analysis

wordpress.org/plugins/hijri

Display Hijri and/or Gregorian dates on your blog.

10 active installs v1.1 PHP + WP 2.5+ Updated Feb 5, 2011
arabiccalendardategregorianhijri
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Hijri Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 15yr ago
Risk Assessment

The "hijri" plugin v1.1 presents a concerning security posture despite an apparent absence of known vulnerabilities. The static analysis reveals a significant weakness: 100% of SQL queries are not using prepared statements, a critical flaw that opens the door to SQL injection attacks. Additionally, 100% of output escaping is missing, creating a high risk of Cross-Site Scripting (XSS) vulnerabilities. The presence of file operations without explicit checks also warrants attention, as it could be exploited for unauthorized file manipulation if an attacker can control the path. The lack of any recorded historical vulnerabilities might suggest a low profile or diligent maintenance, but it does not negate the serious coding practices observed in the static analysis. The plugin's limited attack surface (0 entry points) is a positive aspect, but it is overshadowed by the severe code-level risks.

Key Concerns

  • SQL queries not using prepared statements
  • Output escaping not properly implemented
  • File operations present
  • No nonce checks
  • No capability checks
Vulnerabilities
None known

Hijri Security Vulnerabilities

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

Hijri Code Analysis

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

SQL Query Safety

0% prepared2 total queries

Output Escaping

0% escaped2 total outputs
Data Flows
2 unsanitized

Data Flow Analysis

2 flows2 with unsanitized paths
hijriSettings (hijri.php:106)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Hijri Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 8
actionadmin_menuhijri.php:22
actioninithijri.php:26
filterthe_datehijri.php:30
filterget_the_timehijri.php:31
filterget_the_datehijri.php:32
filterget_comment_datehijri.php:34
filtercomment_timehijri.php:35
actionadmin_noticeshijri.php:40
Maintenance & Trust

Hijri Maintenance & Trust

Maintenance Signals

WordPress version tested3.1.4
Last updatedFeb 5, 2011
PHP min version
Downloads6K

Community Trust

Rating100/100
Number of ratings2
Active installs10
Developer Profile

Hijri Developer Profile

holooli

3 plugins · 30 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

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

Asset Fingerprints

Asset Paths
/hijri/css/style.css/hijri/img/gregorian.gif/hijri/img/hijri.gif

HTML / DOM Fingerprints

CSS Classes
hijri-warningitem
Data Attributes
name="form_gregorian"name="form_hijri"name="form_algorithm"value="hijri_update"name="form_gregorian"value="gregorian"+6 more
FAQ

Frequently Asked Questions about Hijri