Hreflang for polylang Security & Risk Analysis

wordpress.org/plugins/hreflang-for-polylang

Auto print in header the link alternate hreflang of all the language in the website.

100 active installs v1.2 PHP + WP 3.8+ Updated May 15, 2017
alternatehreflanglink-alternatemultilanguagepolylang
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Hreflang for polylang Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 8yr ago
Risk Assessment

The "hreflang-for-polylang" plugin v1.2 exhibits a generally strong security posture based on the provided static analysis. The absence of any identified attack surface points, dangerous functions, file operations, or external HTTP requests is a positive indicator. Furthermore, all SQL queries utilize prepared statements, mitigating the risk of SQL injection vulnerabilities. The lack of any recorded CVEs or past vulnerabilities is also encouraging.

However, a significant concern arises from the output escaping analysis. With one total output identified and 0% properly escaped, this indicates a clear risk of cross-site scripting (XSS) vulnerabilities. Any data processed and displayed by this plugin that is not properly sanitized before output could be exploited by attackers to inject malicious scripts into users' browsers. The lack of any capability checks or nonce checks, while not directly indicated as a risk due to the absence of an attack surface, means that if any entry points were to be introduced in future versions, they would be unprotected.

In conclusion, while the plugin has a clean vulnerability history and avoids many common pitfalls, the critical lack of output escaping presents a tangible security risk. Addressing this specific issue should be the immediate priority to improve the plugin's overall security. The absence of known vulnerabilities suggests good development practices in other areas, but the XSS potential needs urgent attention.

Key Concerns

  • Unescaped output identified
Vulnerabilities
None known

Hreflang for polylang Security Vulnerabilities

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

Hreflang for polylang Code Analysis

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

Output Escaping

0% escaped1 total outputs
Attack Surface

Hreflang for polylang Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 1
actionwp_headhreflang_for_polylang.php:46
Maintenance & Trust

Hreflang for polylang Maintenance & Trust

Maintenance Signals

WordPress version tested4.7.32
Last updatedMay 15, 2017
PHP min version
Downloads72K

Community Trust

Rating0/100
Number of ratings0
Active installs100
Developer Profile

Hreflang for polylang Developer Profile

Marco Giannini

1 plugin · 100 total installs

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

How We Detect Hreflang for polylang

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

Asset Fingerprints

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Hreflang for polylang