# CVE-2026-94239: Loco Translate < 2.8.9 - Translator+ Stored XSS via Bundle Configuration

> Stored XSS in Loco Translate allows translators to inject scripts into admin pages, potentially compromising administrator accounts.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Oct 2026
- **Updated:** 3 Oct 2026
- **Also known as:** GHSA-xmgg-47vp-73xr

## What is CVE-2026-94239?

CVE-2026-94239 is a medium-severity cross-site scripting vulnerability in Unknown Loco Translate, published on 3 Oct 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The Loco Translate WordPress plugin before 2.8.9 does not sanitise and escape some bundle configuration values before outputting them back in an admin page, allowing users with the translator capability and above to perform Stored Cross-Site Scripting attacks against high privilege users such as administrators.

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

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


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

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

## Is CVE-2026-94239 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94239 is a medium-severity cross-site scripting vulnerability in Unknown Loco Translate, published on 3 Oct 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-94239 in the wild and no public exploit code.

Affected product: Unknown Loco Translate. 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-94239/ (Markdown: https://insights.sbomify.com/CVE-2026-94239/index.md)
```

## Sources

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

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