AutoHan Security & Risk Analysis

wordpress.org/plugins/autohan

Automatically switch to traditional Han characters (Kanji|Hanzi|漢字|汉字), or simplified Han characters, which the website visitor is more accustomed to.

300 active installs v0.6 PHP 7.0+ WP 5.7.2+ Updated Sep 9, 2025
autohanchinesehanjihanzitranslation
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is AutoHan Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs Updated 8mo ago
Risk Assessment

The autohan v0.6 plugin exhibits a concerning security posture despite a lack of recorded historical vulnerabilities. The static analysis reveals a significant weakness in output escaping, with 100% of identified output not being properly escaped. This represents a critical vulnerability vector, potentially leading to Cross-Site Scripting (XSS) attacks if any of the output is influenced by user-supplied data. While the absence of dangerous functions, raw SQL queries, file operations, external HTTP requests, and a lack of a large attack surface are positive indicators, the failure to escape output is a fundamental security lapse. The taint analysis also indicates a flow with an unsanitized path, reinforcing the risk of data being processed without proper validation or sanitization before output. The lack of vulnerability history, while seemingly positive, could also indicate a lack of rigorous security auditing or that the plugin's limited functionality has not yet been a target for exploitation. However, based on the static analysis, the unescaped output is a clear and present danger.

Key Concerns

  • 100% of outputs unescaped
  • Flow with unsanitized path
Vulnerabilities
None known

AutoHan Security Vulnerabilities

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

AutoHan Release Timeline

v0.21
v0.6Current
v0.5
v0.4
v0.3
v0.2
v0.1
Code Analysis
Analyzed Mar 16, 2026

AutoHan Code Analysis

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

Output Escaping

0% escaped3 total outputs
Data Flows · Security
1 unsanitized

Data Flow Analysis

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

AutoHan Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 3
actioninitautohan.php:13
actionwp_footerautohan.php:66
actionadmin_menuautohan.php:70
Maintenance & Trust

AutoHan Maintenance & Trust

Maintenance Signals

WordPress version tested6.8.5
Last updatedSep 9, 2025
PHP min version7.0
Downloads11K

Community Trust

Rating80/100
Number of ratings1
Active installs300
Developer Profile

AutoHan Developer Profile

zuola

1 plugin · 300 total installs

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

How We Detect AutoHan

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/autohan/images/logo.svg/wp-content/plugins/autohan/images/line_donate.svg/wp-content/plugins/autohan/images/paypal_donate.svg/wp-content/plugins/autohan/images/alipay_donate_t.svg/wp-content/plugins/autohan/images/wechat_donate.svg/wp-content/plugins/autohan/images/cash_donate.svg
Script Paths
/wp-content/plugins/autohan/Std_StranJF.php

HTML / DOM Fingerprints

Data Attributes
id="AutoHan"
JS Globals
StranBody
Shortcode Output
<a href='javascript:AutoHan()' id='AutoHan'>繁体汉文</a>
FAQ

Frequently Asked Questions about AutoHan