dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-9109

HIGH · 7.2 CVSS v3.1 Published 2026-06-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The GPTranslate – Multilingual AI Translation for WordPress: Automatically Translate Websites plugin for WordPress is vulnerable to Stored Cross-Site Scripting via REST API Translation Storage in all versions up to, and including, 2.31 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The deterministically derived API key (sha256 of the site URL) is printed in the HTML source of every page via the JavaScript variable gptApiKey, meaning any unauthenticated visitor can retrieve the key and submit malicious translation payloads to the /wp-json/gptranslate/v1/request endpoint without any additional precondition.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The GPTranslate WordPress plugin (versions up to 2.31) has a stored XSS vulnerability in its REST API translation storage endpoint (/wp-json/gptranslate/v1/request). Unauthenticated attackers can retrieve the site's API key (deterministically derived as sha256 of the site URL and exposed in HTML via gptApiKey variable) and inject malicious JavaScript through translation payloads due to insufficient input sanitization and output escaping.

MitigationImplement proper input sanitization (sanitize_text_field, wp_kses) on all translation payload inputs and proper output escaping (esc_html, esc_attr) when displaying translations. Consider replacing the deterministic API key derivation with a randomly generated key.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify GPTranslate plugin installation and version
    Check the WordPress plugin directory or wp-content/plugins folder for the gptranslate folder, and read the main plugin file (e.g., gptranslate.php) to find the version number declared in the plugin header
    Affected if The installed version is 2.31 or lower (any version up to and including 2.31)
  2. Look for exposed API key in page source
    View the HTML source of any page on the WordPress site and search for the JavaScript variable 'gptApiKey'
    Affected if The variable gptApiKey is present and contains a sha256 hash value on pages
  3. Verify vulnerable REST API endpoint exists
    Send a GET request to /wp-json/gptranslate/v1/request and confirm the endpoint responds (even with an error)
    Affected if The endpoint /wp-json/gptranslate/v1/request exists and responds without requiring authentication
  4. Check for injected translation payloads in stored content
    Inspect the WordPress database table where translations are stored (typically related to gptranslate options or a custom table) or use WordPress admin to view translation entries if exposed
    Affected if Stored translation entries contain suspicious JavaScript code, HTML script tags, or event handler attributes (onerror, onclick, etc.)

A user is affected if GPTranslate plugin version 2.31 or lower is installed, the gptApiKey JavaScript variable is exposed on pages, and the /wp-json/gptranslate/v1/request endpoint accepts unauthenticated requests with malicious translation payloads now stored in the database.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input sanitization (sanitize_text_field, wp_kses) on all translation payload inputs and proper output escaping (esc_html, esc_attr) when displaying translations. Consider replacing the deterministic API key derivation with a randomly generated key.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9109 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9109 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data