Badge for GlotPress Security & Risk Analysis

wordpress.org/plugins/badge-for-glotpress

Generate badges for GloPress in your projects

0 active installs v1.0.2 PHP + WP 5.0+ Updated Dec 10, 2025
badgegitglotpresstranslationversion
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Badge for GlotPress Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs Updated 3mo ago
Risk Assessment

The "badge-for-glotpress" plugin exhibits several concerning security weaknesses despite a lack of known historical vulnerabilities. The static analysis reveals a significant attack surface, with two AJAX handlers identified as entry points, both of which lack proper authentication checks. This absence of authorization on AJAX endpoints represents a critical risk, as it allows any unauthenticated user to trigger these functions, potentially leading to unauthorized actions or information disclosure.

While the plugin demonstrates good practices by using prepared statements for all SQL queries and not bundling external libraries, the unescaped output on 50% of its outputs is a notable concern. This could lead to Cross-Site Scripting (XSS) vulnerabilities if user-supplied data is not properly sanitized before being displayed. The lack of nonce checks on AJAX handlers exacerbates this risk, as malicious scripts could be injected and executed without any validation. The absence of capability checks further compounds the authorization issue.

Given the absence of past CVEs, the plugin might appear secure, but this can also indicate that vulnerabilities have simply not been discovered or reported yet. The current static analysis findings, particularly the unprotected AJAX endpoints and unescaped output, point to a fragile security posture that requires immediate attention. The plugin's strengths lie in its SQL query handling and absence of bundled libraries, but these are overshadowed by the critical lack of authentication and authorization on its primary entry points.

Key Concerns

  • AJAX handlers without authentication checks
  • AJAX handlers without capability checks
  • Unescaped output on 50% of outputs
  • AJAX handlers without nonce checks
Vulnerabilities
None known

Badge for GlotPress Security Vulnerabilities

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

Badge for GlotPress Code Analysis

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

Output Escaping

50% escaped2 total outputs
Attack Surface
2 unprotected

Badge for GlotPress Attack Surface

Entry Points2
Unprotected2

AJAX Handlers 2

authwp_ajax_badge4glotpressgp-badge.php:16
noprivwp_ajax_badge4glotpressgp-badge.php:17
WordPress Hooks 3
actioninitgp-badge.php:18
filterquery_varsgp-badge.php:19
actionwpgp-badge.php:20
Maintenance & Trust

Badge for GlotPress Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.4
Last updatedDec 10, 2025
PHP min version
Downloads1K

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

Badge for GlotPress Developer Profile

Bastien Ho

12 plugins · 2K total installs

86
trust score
Avg Security Score
88/100
Avg Patch Time
15 days
View full developer profile
Detection Fingerprints

How We Detect Badge for GlotPress

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

Asset Fingerprints

HTML / DOM Fingerprints

REST Endpoints
/glotpress/api/projects/(.*)
FAQ

Frequently Asked Questions about Badge for GlotPress