Ichigen San Security & Risk Analysis

wordpress.org/plugins/ichigen-san

Private publishing

200 active installs v0.3 PHP + WP 3.4+ Updated Sep 4, 2014
maintenanceprivate
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Ichigen San Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 11yr ago
Risk Assessment

The plugin 'ichigen-san' v0.3 exhibits a generally good security posture based on the static analysis provided. The absence of any identified AJAX handlers, REST API routes, shortcodes, or cron events with unprotected entry points is a significant strength. Furthermore, the code shows no indications of dangerous functions, raw SQL queries, file operations, external HTTP requests, or bundled libraries, all of which are positive security indicators. The vulnerability history is also clean, with no known CVEs or past security incidents, suggesting a well-maintained and secure development practice.

However, the static analysis does reveal a significant concern regarding output escaping. With only 29% of outputs being properly escaped, there is a high risk of cross-site scripting (XSS) vulnerabilities. Any user-supplied data that is not properly escaped before being displayed on the front-end or admin area could be exploited by attackers to inject malicious scripts. While there are no direct evidence of taint flows or unsanitized paths in this specific analysis, the poor output escaping practices could easily lead to such vulnerabilities if user input is not handled with extreme care.

In conclusion, while 'ichigen-san' v0.3 demonstrates strong foundational security practices by minimizing its attack surface and avoiding common risky coding patterns, the significant deficit in output escaping presents a critical security weakness. This aspect requires immediate attention to prevent potential XSS attacks. The absence of past vulnerabilities is encouraging, but it does not negate the current risks identified.

Key Concerns

  • Low output escaping
Vulnerabilities
None known

Ichigen San Security Vulnerabilities

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

Ichigen San Code Analysis

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

Output Escaping

29% escaped7 total outputs
Attack Surface

Ichigen San Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 4
actiontemplate_redirectichigen-san.php:41
actionadmin_menuichigen-san.php:43
actionadmin_initichigen-san.php:44
filteradmin_initichigen-san.php:45
Maintenance & Trust

Ichigen San Maintenance & Trust

Maintenance Signals

WordPress version tested3.9.40
Last updatedSep 4, 2014
PHP min version
Downloads4K

Community Trust

Rating100/100
Number of ratings2
Active installs200
Developer Profile

Ichigen San Developer Profile

webnist

2 plugins · 400 total installs

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

How We Detect Ichigen San

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/ichigen-san/images/icon/menu.png
Script Paths
/wp-content/plugins/ichigen-san/js/ichigen-san.js
Version Parameters
ichigen-san/js/ichigen-san.js?ver=

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Ichigen San