Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-59167 critical CVSS 10.0

Cross-Site Scripting (XSS) in suneditor (CVE-2026-59167)

Summary

Cross-site scripting in suneditor (CVE-2026-59167). Successful exploitation can lead to full system takeover. Exploitable via onclick. Mitigation: upgrade to 2.47.11 or later.

Original description

The description as published by the source.

Summary

SUNEDITOR v2.47.10 appears to allow JavaScript execution through crafted namespaced HTML elements.

The sanitization logic does not fully remove executable event-handler attributes from certain custom/namespaced tags. As a result, an attacker may be able to inject HTML content that executes JavaScript when the rendered element is interacted with.

This behavior was observed after the changes introduced in this commit:

https://github.com/JiHong88/suneditor/commit/9ed405fb0de676e56cd0e6a13c19c103ad5948d3

Affected Version

Confirmed vulnerable:

  • SUNEDITOR =< 2.47.10

Potentially affected:

  • Previous versions, if the same sanitization logic is still present

Proof of Concept

The following payload preserves an executable event handler:


click

Simplified PoC:

click

📎 Click here for solutions

Steps to Reproduce

  1. Open SUNEDITOR using version 2.47.10.
  2. Insert the payload above into the editor.
  3. Save or render the generated content.
  4. Click the generated element.
  5. Observe that JavaScript is executed.

Impact

This may allow an attacker to inject arbitrary JavaScript into rendered editor content.

Depending on how SUNEDITOR is integrated into an application, this could lead to:

  • Stored XSS
  • DOM manipulation
  • Session theft
  • Credential theft
  • Account takeover actions performed in the victim’s browser context

Technical Details

The issue appears to be related to incompl…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-59167 has been found in suneditor.
Attackers can target a specific entry point like onclick over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 10.0/10.
What to do: upgrade suneditor to 2.47.11 or later.
If unsure, ask your IT team or search "suneditor CVE-2026-59167" on the vendor's site.

CVE-2026-59167 (suneditor) — CWE-79 / CVSS v3 10.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: onclick
Patched: 2.47.11 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in suneditor. Attackers reach the vulnerable code path via onclick without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of suneditor. Attack surface: onclick.

🔥 Severity

Severity: Critical (CVSS 10.0/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 2.47.11.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'suneditor' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'suneditor' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で suneditor を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade suneditor to 2.47.11

    ステージング環境で 2.47.11 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm suneditor
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.47.11"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details