CVE-2026-89278
MediumCVSS 5.3Exploitation Probability (EPSS)
Low risk17th percentile - higher than 17% of all known CVEs
Summary
The GPTranslate plugin for WordPress in all versions up to and including 2.34.6 is vulnerable to Sensitive Information Exposure via enqueue_frontend_scripts. Unauthenticated attackers can extract the plaintext third-party AI provider API key (OpenAI, DeepL, xAI/Grok, Gemini, Claude, or Google Cloud Translation) by fetching any public page and applying the inverse transformation bundled in the plugin's own public JavaScript asset. This affects the default configuration and all supported non-DeepSeek providers.
Risk Assessment
Exposure of the AI provider API key allows attackers to use the organization's billed account, causing uncontrolled costs and potential abuse. The key may also grant access to other resources tied to that account.
Recommendation
Update the GPTranslate plugin to a version later than 2.34.6. Immediately revoke and regenerate API keys with all AI providers and consider switching to server-proxy mode.
Other vulnerabilities in GPTranslate WordPress plugin
Original NVD description (English source)
The GPTranslate – Multilingual AI Translation Agent for WordPress: Translate Your Site with AI plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.34.6 via the enqueue_frontend_scripts. This makes it possible for unauthenticated attackers to extract the plaintext third-party AI provider API key (OpenAI, DeepL, xAI/Grok, Gemini, Claude, or Google Cloud Translation) — a credential granting billed account access — by fetching any public page and applying the inverse transformation bundled in the plugin's own public JavaScript asset. This exposure affects the default configuration (gpt-3.5-turbo in client mode) and all supported non-DeepSeek providers; only deepseek-* models and gpt-* models configured in server-proxy mode correctly suppress key emission.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS

