# CVE-2026-103309: GPTranslate < 2.34.14 - Unauthenticated Stored XSS via REST API Translation Storage

> Unauthenticated attackers can inject malicious scripts via the REST API when server-side translations are enabled, potentially compromising user sessions.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-5r7v-q722-2v82

## What is CVE-2026-103309?

CVE-2026-103309 is a high-severity cross-site scripting vulnerability in Unknown GPTranslate, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The GPTranslate  WordPress plugin before 2.34.14 does not properly restrict who can store translations, and does not escape them when outputting them in translated pages, allowing unauthenticated users to perform Stored Cross-Site Scripting attacks when server-side translations are enabled.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-103309?


## How do I fix CVE-2026-103309?

No fix has been published for CVE-2026-103309 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-103309 being exploited?

There is no known exploitation of CVE-2026-103309 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-103309 and fix it if it is affected.

What it is: CVE-2026-103309 is a high-severity cross-site scripting vulnerability in Unknown GPTranslate, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-103309 in the wild and no public exploit code.

Affected product: Unknown GPTranslate. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-103309/ (Markdown: https://insights.sbomify.com/CVE-2026-103309/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-103309
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-103309
- OSV: https://osv.dev/vulnerability/CVE-2026-103309

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-103309/
Summaries are generated and may contain mistakes; the official description above is the record.