# CVE-2026-124494: SunEditor before 3.4.0 Stored XSS via : Entity Sanitizer Bypass


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 8 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-cm78-x5pp-rjx2, GHSA-v4jx-8pj6-w4w8

## What is CVE-2026-124494?

CVE-2026-124494 is a critical vulnerability in JiHong88 suneditor, published on 8 Nov 2026. 

### Official description

SunEditor before 3.4.0 contains a stored cross-site scripting vulnerability because the html.clean() sanitizer's _normalizeURL() function decodes named entities like : to an empty string. Attackers can inject href values such as javascript: that pass the _isSafeURL() check but are decoded by browsers, executing JavaScript when victims click stored links.

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

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


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

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

## Is CVE-2026-124494 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-124494 is a critical vulnerability in JiHong88 suneditor, published on 8 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-124494 in the wild and no public exploit code.

Affected product: JiHong88 suneditor. 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-124494/ (Markdown: https://insights.sbomify.com/CVE-2026-124494/index.md)
```

## Sources

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

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