AI Translate For Polylang Security & Risk Analysis

wordpress.org/plugins/ai-translate-for-polylang

Add auto AI translation caperbility to Polylang using OpenAI/ChatGPT or Anthropic/Claude.

100 active installs v1.1.6 PHP + WP 3.0+ Updated Apr 3, 2026
languagemultilingualpolylangtranslatetranslation
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is AI Translate For Polylang Safe to Use in 2026?

Generally Safe

Score 100/100

AI Translate For Polylang has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 1mo ago
Risk Assessment

The 'ai-translate-for-polylang' plugin, version 1.1.3, presents a generally positive security posture based on the static analysis and vulnerability history provided. The plugin demonstrates strong adherence to secure coding practices, with no identified dangerous functions, SQL queries utilizing prepared statements, and a complete absence of known CVEs. The limited attack surface, with no exposed AJAX handlers, REST API routes, shortcodes, or cron events without authentication, further contributes to its robust security.

However, a few areas warrant attention. The taint analysis identified one flow with an unsanitized path, which, while not reaching critical or high severity in this instance, represents a potential weakness if exploited. Additionally, the output escaping, while mostly proper, has a portion that is not, posing a minor risk of cross-site scripting (XSS) vulnerabilities. The single external HTTP request also introduces a potential dependency risk if the target endpoint is compromised.

Overall, 'ai-translate-for-polylang' v1.1.3 appears to be a secure plugin with a clean vulnerability history. The identified areas for improvement are minor and do not suggest immediate critical threats. Continued vigilance and addressing the minor findings in output escaping and taint analysis would further solidify its security.

Key Concerns

  • Taint flow with unsanitized path
  • Non-properly escaped output detected
  • External HTTP request present
Vulnerabilities
None known

AI Translate For Polylang Security Vulnerabilities

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

AI Translate For Polylang Release Timeline

v1.1.6Current
v1.1.5
v1.1.4
v1.1.3
v1.1.2
v1.1.1
v1.1.0
v1.0.9
v1.0.8
v1.0.7
v1.0.6
v1.0.5
v1.0.4
v1.0.3
v1.0.2
v1.0.1
v1.0.0
Code Analysis
Analyzed Mar 16, 2026

AI Translate For Polylang Code Analysis

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

Output Escaping

71% escaped28 total outputs
Data Flows · Security
1 unsanitized

Data Flow Analysis

2 flows1 with unsanitized paths
menu_page (inc\settingslib.php:140)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

AI Translate For Polylang Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 7
actioninitai-translate-polylang.php:53
filterdefault_titleai-translate-polylang.php:54
filterdefault_contentai-translate-polylang.php:55
filterpll_translate_post_metaai-translate-polylang.php:57
filterwp_insert_post_dataai-translate-polylang.php:212
actionadmin_initinc\settingslib.php:24
actionadmin_menuinc\settingslib.php:25
Maintenance & Trust

AI Translate For Polylang Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.0
Last updatedApr 3, 2026
PHP min version
Downloads3K

Community Trust

Rating86/100
Number of ratings6
Active installs100
Developer Profile

AI Translate For Polylang Developer Profile

jamesdlow

14 plugins · 400 total installs

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

How We Detect AI Translate For Polylang

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

Asset Fingerprints

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about AI Translate For Polylang