# code16/sharp has a stored XSS via data-html-content Sanitizer Bypass

Advisory record · `GHSA-vj3q-vp3g-j9c8`

- **Identifiers:** `GHSA-vj3q-vp3g-j9c8` · `CVE-2026-61825` · `PKSA-p6zx-3z97-z7f8`
- **State:** Confirmed
- **Severity:** CVSS 8.7 High
- **Critical:** No
- **Weakness (CWE):** [CWE-79](https://cwe.mitre.org/data/definitions/79.html)
- **Tags:** [Cross-site scripting (XSS)](https://agentprime.io/advisories/tag/xss.md)
- **Published:** 25 Sept 2026
- **Updated:** 25 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 25 Sept 2026, 15:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `code16/sharp` (Packagist): affected `<9.22.5`; fixed in `9.22.5`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Versions of code16/sharp before 9.22.5 (Packagist) contain a stored cross-site scripting flaw in which the HTML sanitizer of SharpEditorFormField can be bypassed using the data-html-content attribute. The source does not say what privileges an attacker needs to store the content. Upgrade to code16/sharp 9.22.5 or later. In that version, the RAW_HTML toolbar button must be explicitly configured to keep the behavior, and applications using it must sanitize field content manually, for example with Symfony/HtmlSanitizer.

Written 31 Oct 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.7 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0023, the 14th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 13:54 UTC: First seen by agentprime
- 31 Oct 2026, 13:54 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-vj3q-vp3g-j9c8)

## Sources

- [GitHub Advisory Database: GHSA-vj3q-vp3g-j9c8](https://github.com/advisories/GHSA-vj3q-vp3g-j9c8)
- [OSV: GHSA-vj3q-vp3g-j9c8](https://osv.dev/vulnerability/GHSA-vj3q-vp3g-j9c8)
- <https://github.com/code16/sharp/security/advisories/GHSA-vj3q-vp3g-j9c8>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-61825>
- <https://github.com/code16/sharp/commit/ec509a22c808a5bd9dfad6a0a85c92ce6f411e21>
- <https://github.com/code16/sharp>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-vj3q-vp3g-j9c8>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-vj3q-vp3g-j9c8/>. Everything for agents: <https://agentprime.io/llms.txt>.