# CVE-2026-88784: Weglot < 6.4.3 - Unauthenticated Stored XSS via Translated Page Link Rewriting


- **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
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-v5cq-8fvv-9wcc

## What is CVE-2026-88784?

CVE-2026-88784 is a high-severity vulnerability in Unknown Translate WordPress with Weglot 2.0, published on 21 Oct 2026. 

### Official description

The Translate WordPress with Weglot 2.0  WordPress plugin before 6.4.3 does not escape the URLs it re-inserts into a page when rewriting links for a translated language, and reverses the encoding that was applied to them beforehand, allowing unauthenticated users to store a payload which executes in the browser of anyone viewing the page in a translated language.

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

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


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

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

## Is CVE-2026-88784 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-88784 is a high-severity vulnerability in Unknown Translate WordPress with Weglot 2.0, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-88784 in the wild and no public exploit code.

Affected product: Unknown Translate WordPress with Weglot 2.0. 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-88784/ (Markdown: https://insights.sbomify.com/CVE-2026-88784/index.md)
```

## Sources

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

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