Domain-translate Security & Risk Analysis

wordpress.org/plugins/domain-translate

The automatic translation of a WordPress website based on its domain.

0 active installs v1.2.0 PHP 8.2.0+ WP 6.7+ Updated Dec 15, 2025
automatic-translategoogle-translatetranslate-domains
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Domain-translate Safe to Use in 2026?

Generally Safe

Score 100/100

Domain-translate 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 domain-translate v1.2.0 plugin demonstrates an excellent security posture based on the provided static analysis. The absence of any identified entry points such as AJAX handlers, REST API routes, shortcodes, or cron events significantly limits the potential attack surface. Furthermore, the code exhibits strong secure coding practices, with 100% of SQL queries using prepared statements and all output properly escaped, mitigating common vulnerabilities like SQL injection and cross-site scripting. The lack of file operations and external HTTP requests also reduces exposure to certain attack vectors. The vulnerability history being entirely clean with no recorded CVEs further reinforces a perception of a secure plugin. However, the complete absence of nonce checks across any potential entry points (though none were identified) is a noteworthy omission, as is the single capability check without other authentication mechanisms. While the current analysis doesn't reveal exploitable flaws, the lack of demonstrated authentication on any user-facing features that might exist beyond the analyzed entry points could be a concern if the plugin's functionality extends further than indicated.

Key Concerns

  • No nonce checks found
  • Limited capability checks (only 1)
Vulnerabilities
None known

Domain-translate Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Version History

Domain-translate Release Timeline

v1.2.0Current
Code Analysis
Analyzed Mar 17, 2026

Domain-translate Code Analysis

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

Output Escaping

100% escaped17 total outputs
Attack Surface

Domain-translate Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 4
actioninitdomain-translate.php:63
actionadmin_initdomain-translate.php:64
actionwp_enqueue_scriptssrc\Class\MDT_Frontend.php:36
actionwp_enqueue_scriptssrc\Class\MDT_Frontend.php:37
Maintenance & Trust

Domain-translate Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.4
Last updatedDec 15, 2025
PHP min version8.2.0
Downloads144

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

Domain-translate Developer Profile

Myridia Company

4 plugins · 10 total installs

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

How We Detect Domain-translate

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/domain-translate/js/domain-translate.js/wp-content/plugins/domain-translate/css/domain-translate.css
Script Paths
https://translate.google.com/translate_a/element.js?cb=domain_translate_init
Version Parameters
domain-translate/js/domain-translate.js?ver=domain-translate/css/domain-translate.css?ver=

HTML / DOM Fingerprints

Data Attributes
data-source_lang_codedata-target_lang_codedata-domaindata-domains
JS Globals
domain_translate_datadomain_translate_init
FAQ

Frequently Asked Questions about Domain-translate