# CVE-2026-124492: SunEditor before 3.4.0 Stored XSS via Link Modal Bookmark List


- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 8 Nov 2026
- **Updated:** 8 Nov 2026
- **Also known as:** GHSA-5pp5-5qrp-vq56, GHSA-h8r9-r2r8-gxj7

## What is CVE-2026-124492?

CVE-2026-124492 is a high-severity vulnerability in JiHong88 suneditor, published on 8 Nov 2026. 

### Official description

SunEditor before 3.4.0 contains a stored cross-site scripting vulnerability in ModalAnchorEditor's #createBookmarkList, which inserts entity-decoded h1-h6 header textContent into the bookmark list via innerHTML without escaping. Attackers can store HTML-encoded payloads in editor headers that execute JavaScript when a victim opens the link modal and types # in the URL input.

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

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


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

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

## Is CVE-2026-124492 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-124492 is a high-severity vulnerability in JiHong88 suneditor, published on 8 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-124492 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-124492/ (Markdown: https://insights.sbomify.com/CVE-2026-124492/index.md)
```

## Sources

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

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