Cross-Site Scripting (XSS) in code16/sharp (CVE-2026-61825)
Summary
Cross-site scripting in code16/sharp (CVE-2026-61825). Confidential information can be exposed externally. Exploitable via SharpEditorFormField. Mitigation: upgrade to 9.22.5 or later.
Original description
The description as published by the source.
Impact
The vulnerability allows an attacker to bypass the HTML sanitizer by using the data-html-content attribute in the content of a SharpEditorFormField.
Patches
The field must now explicitly configure SharpFormEditorField::RAW_HTML in the toolbar to keep this behavior. When using the RAW_HTML button, the application using code16/sharp must sanitize manually the content coming from the field.
Vulnerability has been patched in version 9.22.5.
Workarounds
Sanitize every contents of editors manually (e.g. using Symfony/HtmlSanitizer)
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-61825 has been found in code16/sharp.
Attackers can target a specific entry point like SharpEditorFormField over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.7/10.
What to do: upgrade code16/sharp to 9.22.5 or later.
If unsure, ask your IT team or search "code16/sharp CVE-2026-61825" on the vendor's site.
CVE-2026-61825 (code16/sharp) — CWE-79 / CVSS v3 8.7
Attack vector: remote (network-reachable)
Attack surface: SharpEditorFormField / RAW_HTML
Patched: 9.22.5 — apply immediately
Workaround: Sanitize every contents of editors manually (e.g.
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.
Cross-site scripting (XSS) (CWE-79) exists in code16/sharp. Attackers reach the vulnerable code path via SharpEditorFormField.
Check the vendor advisory for the affected versions of code16/sharp. Attack surface: SharpEditorFormField / RAW_HTML.
Severity: High (CVSS 8.7/10). Confidential information can be exposed externally.
Update to 9.22.5.
Workaround: Sanitize every contents of editors manually (e.g.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'code16/sharp' . 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
-
1Identify exposure identify
grep -r 'code16/sharp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
code16/sharpを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Sanitize every contents of editors manually (e.g.パッチが適用されるまでの応急処置として、Sanitize every contents of editors manually (e.g. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade code16/sharp to 9.22.5ステージング環境で 9.22.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com