Post Title Furigana Security & Risk Analysis

wordpress.org/plugins/post-title-furigana

Automatically set Japanese Reading title into the custom field.

10 active installs v1.0 PHP + WP 3.5+ Updated Nov 14, 2013
admincustom-fieldlanguagepostyahoo
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Post Title Furigana Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 12yr ago
Risk Assessment

The "post-title-furigana" plugin v1.0 exhibits a mixed security posture. On the positive side, it demonstrates good practices by using prepared statements for all SQL queries and does not appear to have any publicly known vulnerabilities. The absence of external HTTP requests and bundled libraries further reduces potential attack vectors. However, significant concerns arise from the plugin's attack surface. It possesses two AJAX handlers, both of which lack authentication checks, presenting a clear opportunity for unauthorized actions. Furthermore, the taint analysis revealed two flows with unsanitized paths, indicating a potential for privilege escalation or other security issues if these paths are exposed to user input. The low percentage of properly escaped output also raises alarms, as it could lead to cross-site scripting (XSS) vulnerabilities.

Key Concerns

  • AJAX handlers without authentication
  • Taint flows with unsanitized paths
  • Low percentage of output escaping
  • Missing nonce checks on AJAX
Vulnerabilities
None known

Post Title Furigana Security Vulnerabilities

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

Post Title Furigana Code Analysis

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

Output Escaping

8% escaped12 total outputs
Data Flows
2 unsanitized

Data Flow Analysis

4 flows2 with unsanitized paths
config_page (post-title-furigana.php:74)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface
2 unprotected

Post Title Furigana Attack Surface

Entry Points2
Unprotected2

AJAX Handlers 2

authwp_ajax_post-title-furiganapost-title-furigana.php:37
noprivwp_ajax_post-title-furiganapost-title-furigana.php:38
WordPress Hooks 8
actioninitpost-title-furigana.php:31
actionadmin_print_scriptspost-title-furigana.php:32
actionedit_form_after_titlepost-title-furigana.php:33
actionsave_postpost-title-furigana.php:34
actionpublish_postpost-title-furigana.php:35
actiondelete_postpost-title-furigana.php:36
actionadmin_menupost-title-furigana.php:46
filterplugin_action_linkspost-title-furigana.php:54
Maintenance & Trust

Post Title Furigana Maintenance & Trust

Maintenance Signals

WordPress version tested3.7.41
Last updatedNov 14, 2013
PHP min version
Downloads1K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Post Title Furigana Developer Profile

sysbird

4 plugins · 200 total installs

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

How We Detect Post Title Furigana

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/post-title-furigana/post-title-furigana.js
Script Paths
/wp-content/plugins/post-title-furigana/post-title-furigana.js
Version Parameters
post-title-furigana/post-title-furigana.js?ver=

HTML / DOM Fingerprints

CSS Classes
wraper-post-title-furigana
Data Attributes
id="ptf_furigana"name="ptf_furigana"id="ptf_ajax_url"name="ptf_ajax_url"
JS Globals
ptf_ajax_url
FAQ

Frequently Asked Questions about Post Title Furigana