SunEditor stored XSS in editor document header handling
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 3.4.0
- Who is exposed
- Specific setups only
Summary
SunEditor before 3.4.0 contains a stored cross-site scripting vulnerability in the DocumentType constructor that injects header textContent into innerHTML without HTML escaping. Attackers can store entity-encoded HTML in h1-h6 headers that executes JavaScript when editors using document:header mode initialize, enabling session cookie theft.
Who should check
Teams running SunEditor (suneditor npm package) 3.3.1 or earlier with type 'document:header' or 'document:header,page' configured, where editors load stored header content.
“Affected versions <=v3.3.1”
What to do
Check whether your setup matches what the bug needs.
Editor initialized with type 'document:header' or 'document:header,page' configuration SunEditor version 3.3.1 or earlier (affected versions <=v3.3.1, before 3.4.0)Upgrade to a fixed version: 3.4.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-124493 (SunEditor before 3.4.0 Stored XSS via DocumentType Header textContent), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-124493 (entry last updated 2026-11-12):
Affected:
- JiHong88 suneditor: fixed in 3.4.0
Fixed versions: 3.4.0.
Conditions (all must be true for the bug to be hit):
- Editor initialized with type 'document:header' or 'document:header,page' configuration (source: https://github.com/JiHong88/suneditor/security/advisories/GHSA-h9pq-57qf-vvfh)
- SunEditor version 3.3.1 or earlier (affected versions <=v3.3.1, before 3.4.0) (source: https://github.com/JiHong88/suneditor/security/advisories/GHSA-h9pq-57qf-vvfh)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-124493 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-124493 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/JiHong88/suneditor/security/advisories/GHSA-h9pq-57qf-vvfh
- https://www.vulncheck.com/advisories/suneditor-before-3.4.0-stored-xss-via-documenttype-header-textcontent
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-124493
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-124493"}.Affected versions
- JiHong88 suneditorfixed in 3.4.0
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure15/25Specific setups only, CISA rates it automatable
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.3, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now4 days
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: total
- Record last updated
Public exploit activity
- EPSS: 0.34%
- Posted on X by cve.now Nov 8
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · JiHong88/suneditor · Advisory GHSA-h9pq-57qf-vvfh |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-124493 |
| Record | NVD · CVE-2026-124493 |
| Other links 1 | |
| Link | vulncheck.com · advisories/suneditor-before-3.4.0-stored-xss-via-documenttype-header-textcontent |
Questions about CVE-2026-124493
Is CVE-2026-124493 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
Stored cross-site scripting in SunEditor's document header: content placed through the header textContent can run arbitrary JavaScript in a victim's browser, including reading session cookies via document.cookie and acting on the victim's behalf.
Source: github.com
Which versions are affected by CVE-2026-124493?
suneditor: before 3.4.0.
Source: cve.now feed data
Am I affected, and how do I check?
SunEditor 3.3.1 and earlier (before 3.4.0) are affected, but only when the editor is initialized with type 'document:header' or 'document:header,page'. Check the installed version in the package manifest and look for those type settings in the editor initialization code.
Source: github.com
How do I fix CVE-2026-124493?
Upgrade SunEditor to 3.4.0 or later, which is the fixed version named in the advisory.
Source: github.com
Related
- CVE-2026-59167SunEditor: Critical XSS vulnerability - sanitizer bypass
- CVE-2026-124494SunEditor before 3.4.0 Stored XSS via : Entity Sanitizer Bypass
- CVE-2026-54606SunEditor: DOM XSS in SunEditor Embed Plugin via External Script Element After Iframe Embed
- CVE-2026-124492SunEditor before 3.4.0 Stored XSS via Link Modal Bookmark List
- CVE-2026-124491SunEditor before 3.4.0 Stored XSS via FileUpload Plugin Filename
- CVE-2026-124422SunEditor 3.0.0 before 3.4.0 Stored XSS via html.clean() Iframe Placeholder
No corrections so far. Something wrong on this page? Report an error.