GitHub Advisoryadvisory · npm
GHSA-w93q-cq9w-58p7 SunEditor Embed Plugin has DOM XSS via External Script Element After Iframe Embed
HIGH
Official page ↗
- Aliases
- CVE-2026-54606
- Ecosystem
- npm
- Packages
- suneditor
- Severity
- High
- CVSS vector
- CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- Weaknesses
- CWE-79
- Reviewed
- 2026-08-26
Affected packages
• npm suneditor: >= 3.0.0, < 3.1.4 → fixed in 3.1.4
Description
Summary
A DOM-based Cross-Site Scripting (XSS) vulnerability exists in the SunEditor Embed plugin. Crafted iframe embed HTML followed by an external element bypasses the plugin’s sanitization logic. The plugin recreates and appends the attacker-controlled script element to the live DOM, causing JavaScript execution in the context of the editor page.
If an application stores or reflects SunEditor content without additional backend sanitization, this can lead to stored or reflected XSS when another user opens, previews, renders, or edits the malicious content.
Details
The Embed plugin parses raw embed HTML and processes the resulting DOM nodes. When a element is included after a valid iframe, the plugin creates a new script element using the attacker-controlled src value and appends it to the DOM.
Relevant behavior:
const embedDOM = new DOMParser().parseFromString(src, 'text/html').body.children;
if (/^script$/i.test(chd.nodeName)) {
scriptTag = dom.utils.createElement('script', {
src: chd.getAttribute('src'),
async: 'true'
}, null);
continue;
}
cover.appendChild(scriptTag);
Because the script is newly created and appended, it executes.
PoC
Start a local server hosting a JavaScript payload:
```
mkdir -p /tmp/suneditor-poc
cd /tmp/suneditor-poc
cat > poc.js
`
Successful exploitation is confirmed when:
`alert(1) appears`
or the local server logs:
`GET /poc.js`
Impact
An attacker who can provide or store embed HTML can execute arbitrary JavaScript in another user’s browser when the content is processed by SunEditor. This may allow account actions as the victim, modification of editor content, or access to sensitive data available in the editor page.
The issue is especially impactful when SunEditor content is stored in a backend and later reopened or rendered for administrators, editors, or other users without additional sanitization.
Suggested Fix
Do not recreate or append script elements from user-controlled embed HTML.
Minimum mitigation:
```
if (/^script$/i.test(chd.nodeName)) {
continue;
}
```
A stronger fix is to allow only expected embed elements such as iframe or blockquote, sanitize their attributes, and discard all other sibling elements.
Related
Alias · CVE (1)
- CVE-2026-54606 SunEditor is a lightweight and powerful WYSIWYG editor in vanilla JavaScript with no dependencies. vulnerability
Weakness · CWE (1)
- CWE-79 Improper Neutralization of Input During Web Page Generation weakness
References
- https://github.com/JiHong88/suneditor/security/advisories/GHSA-w93q-cq9w-58p7 web
- https://nvd.nist.gov/vuln/detail/CVE-2026-54606 advisory
- https://github.com/JiHong88/suneditor/issues/1649 web
- https://github.com/github/advisory-database/pull/10757 web
- https://github.com/JiHong88/suneditor/commit/9d43a5e082101d2d6475cba86e0d58d7c2cf6677 web
- https://github.com/JiHong88/suneditor package
- https://github.com/JiHong88/suneditor/releases/tag/3.1.4 web