GP Import Translations from wordress.org Security & Risk Analysis

wordpress.org/plugins/gp-import-from-wp-org

A plugin for GlotPress as a WordPress plugin that imports a language from wordpress.org's translation site.

10 active installs v0.5 PHP + WP 4.4+ Updated Unknown
glotpresstranslation
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is GP Import Translations from wordress.org Safe to Use in 2026?

Generally Safe

Score 100/100

GP Import Translations from wordress.org has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs
Risk Assessment

The "gp-import-from-wp-org" plugin, version 0.5, exhibits a generally good security posture based on the provided static analysis. The plugin has a commendably small attack surface with zero identified entry points, and importantly, zero unprotected entry points. The absence of dangerous functions and the use of prepared statements for all SQL queries are significant strengths. Furthermore, the plugin demonstrates a clean vulnerability history with no recorded CVEs.

However, there are a few areas for concern. The critical signal is that 100% of output is not properly escaped. This means that any dynamic data outputted by the plugin could potentially be vulnerable to Cross-Site Scripting (XSS) attacks if that data is not already sufficiently sanitized before being passed to the output functions. While the plugin has a capability check, it has zero nonce checks, which is a weakness for certain types of operations that might be performed through its limited functionality, especially if any of the file operations involve user-supplied input.

In conclusion, the plugin's minimal attack surface and lack of historical vulnerabilities are positive indicators. The primary concern lies in the unescaped output, which represents a clear XSS risk. The lack of nonce checks also presents a potential, albeit less defined, risk depending on the nature of the file operations. Addressing the output escaping and implementing nonce checks would significantly improve the plugin's overall security.

Key Concerns

  • Output escaping missing
  • Nonce checks missing
Vulnerabilities
None known

GP Import Translations from wordress.org Security Vulnerabilities

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

GP Import Translations from wordress.org Code Analysis

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

Output Escaping

0% escaped1 total outputs
Attack Surface

GP Import Translations from wordress.org Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 2
filtergp_translations_footer_linksgp-import-from-wp-org.php:20
actiongp_initgp-import-from-wp-org.php:94
Maintenance & Trust

GP Import Translations from wordress.org Maintenance & Trust

Maintenance Signals

WordPress version tested6.4.8
Last updatedUnknown
PHP min version
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

GP Import Translations from wordress.org Developer Profile

Greg Ross

34 plugins · 8K total installs

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

How We Detect GP Import Translations from wordress.org

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

Asset Fingerprints

HTML / DOM Fingerprints

Shortcode Output
Import from wordpress.org: [Stable] [Development]
FAQ

Frequently Asked Questions about GP Import Translations from wordress.org