Polyglots Security & Risk Analysis

wordpress.org/plugins/polyglots

Allows to connect your site to translate.wordpress.org

10 active installs v0.1 PHP + WP 3.4+ Updated Sep 14, 2015
admini18npolyglots
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Polyglots Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 10yr ago
Risk Assessment

The "polyglots" v0.1 plugin exhibits a seemingly strong security posture based on the provided static analysis. The complete absence of any identified attack surface points, SQL queries not using prepared statements, and no taint flows suggests a diligent approach to secure coding. The plugin also has a clean vulnerability history with no recorded CVEs, which is a positive indicator. However, the analysis also reveals significant concerns. The extremely low rate of proper output escaping (20%) indicates a high risk of cross-site scripting (XSS) vulnerabilities, as potentially untrusted data could be rendered directly in the browser. Furthermore, the lack of nonce checks and capability checks on any potential entry points, combined with a complete absence of protected entry points (0 unprotected), is a major red flag. While the static analysis reports 0 unprotected entry points, the lack of explicit checks on the few entry points that do exist (even if not explicitly classified as attack vectors in this report) creates an implicit risk. The presence of external HTTP requests without any mention of sanitization or validation also presents a potential for SSRF or other vulnerabilities if the URLs are user-controllable.

Key Concerns

  • Low output escaping rate (20%)
  • No nonce checks on any entry points
  • No capability checks on any entry points
  • External HTTP requests without clear sanitization
Vulnerabilities
None known

Polyglots Security Vulnerabilities

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

Polyglots Code Analysis

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

Output Escaping

20% escaped5 total outputs
Attack Surface

Polyglots Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 8
filterextra_plugin_headersinc\developer.php:16
filterpolyglots_dashboard_countsinc\plugins.php:15
filterplugin_action_linksinc\plugins.php:17
actionafter_plugin_rowinc\plugins.php:18
filterpolyglots_dashboard_countsinc\themes.php:15
actionplugins_loadedpolyglots.php:66
actionadmin_enqueue_scriptspolyglots.php:67
actionwp_dashboard_setuppolyglots.php:68
Maintenance & Trust

Polyglots Maintenance & Trust

Maintenance Signals

WordPress version tested4.3.34
Last updatedSep 14, 2015
PHP min version
Downloads2K

Community Trust

Rating100/100
Number of ratings1
Active installs10
Developer Profile

Polyglots Developer Profile

Marko Heijnen

9 plugins · 870 total installs

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

How We Detect Polyglots

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/polyglots/css/style.css
Version Parameters
polyglots/css/style.css?ver=

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Polyglots