{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-9109 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-9109 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-9109 is a high-severity cross-site scripting vulnerability in john-dagelmore GPTranslate – Multilingual AI Translation for WordPress: Automatically Translate Websites, published on 13 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-9109 and fix it if it is affected.\n\nWhat it is: CVE-2026-9109 is a high-severity cross-site scripting vulnerability in john-dagelmore GPTranslate – Multilingual AI Translation for WordPress: Automatically Translate Websites, published on 13 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-9109 in the wild and no public exploit code.\n\nAffected product: john-dagelmore GPTranslate – Multilingual AI Translation for WordPress: Automatically Translate Websites. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-9109/ (Markdown: https://insights.sbomify.com/CVE-2026-9109/index.md)","id":"CVE-2026-9109","markdown":"https://insights.sbomify.com/CVE-2026-9109/index.md","name":"CVE-2026-9109","record":{"aliases":["GHSA-j66v-hr5c-cjh2"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress translation plugin","requires_auth":"none","summary":"Unauthenticated attackers can inject malicious scripts via the REST API due to exposed API keys, leading to stored XSS and potential account takeover.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"GPTranslate \u003c= 2.31 - Unauthenticated Stored Cross-Site Scripting via REST API Translation Storage","id":"CVE-2026-9109","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":12,"next":{"headline":"Other in Chrome","id":"CVE-2026-9110"},"packages":[],"prev":{"headline":"Studio 5000 Logix Designer® – Multiple Vulnerabilities","id":"CVE-2026-9108"},"products":["GPTranslate – Multilingual AI Translation for WordPress: Automatically Translate Websites"],"published":"2026-06-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-15","vendors":["john-dagelmore"]},"summary":"Unauthenticated attackers can inject malicious scripts via the REST API due to exposed API keys, leading to stored XSS and potential account takeover.","url":"https://insights.sbomify.com/CVE-2026-9109/"}