WP Translation Status Security & Risk Analysis

wordpress.org/plugins/wp-translation

Make a link to GlotPress centralised translation so contributor can help translating the plugin that do not have yet a translation in the local site l …

100 active installs v0.1 PHP + WP 4.0+ Updated Sep 5, 2016
glotpresstranslation
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is WP Translation Status Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 9yr ago
Risk Assessment

The wp-translation v0.1 plugin exhibits a strong security posture based on the provided static analysis data. There are no identified dangerous functions, all SQL queries use prepared statements, and all output is properly escaped. The absence of file operations and external HTTP requests further reduces potential attack vectors. Furthermore, the plugin has no recorded vulnerabilities in its history, suggesting a history of secure development and maintenance.

However, the analysis also highlights some areas for caution. The complete lack of nonce checks and capability checks across all identified entry points is a significant concern. While the current attack surface is zero, any future introduction of AJAX handlers, REST API routes, or shortcodes without these essential security measures could lead to vulnerabilities. The presence of a cron event, while not directly analyzed for security, represents a potential execution point that should be monitored.

In conclusion, wp-translation v0.1 appears secure due to robust coding practices and a clean vulnerability history. The primary weakness lies in the absence of fundamental WordPress security checks like nonces and capability checks. If the plugin's functionality or attack surface expands, addressing these omissions will be critical to maintaining its current good security standing.

Key Concerns

  • Missing nonce checks on entry points
  • Missing capability checks on entry points
Vulnerabilities
None known

WP Translation Status Security Vulnerabilities

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

WP Translation Status Code Analysis

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

WP Translation Status Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 2
actionwpts_daily_eventincludes\cron.php:3
filterplugin_action_linksincludes\main.php:5

Scheduled Events 1

wpts_daily_event
Maintenance & Trust

WP Translation Status Maintenance & Trust

Maintenance Signals

WordPress version tested4.6.30
Last updatedSep 5, 2016
PHP min version
Downloads843

Community Trust

Rating0/100
Number of ratings0
Active installs100
Developer Profile

WP Translation Status Developer Profile

Pascal Casier

2 plugins · 110 total installs

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

How We Detect WP Translation Status

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/wp-translation/css/style.css/wp-content/plugins/wp-translation/js/script.js
Script Paths
/wp-content/plugins/wp-translation/js/script.js
Version Parameters
wp-translation/css/style.css?ver=wp-translation/js/script.js?ver=

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about WP Translation Status