# NanoHTTPD Cross-site Scripting vulnerability

Advisory record · `GHSA-pr5m-4w22-8483`

- **Identifiers:** `GHSA-pr5m-4w22-8483` · `CVE-2020-13697`
- **State:** Confirmed
- **Severity:** No CVSS score
- **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 Feb 2021
- **Updated:** 1 Dec 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 25 Feb 2021, 16:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.nanohttpd:nanohttpd-nanolets` (Maven): affected `<=2.3.1`; no fixed version yet

## Machine-written summary

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

> NanoHTTPD (nanohttpd-nanolets package, Maven org.nanohttpd) versions up to and including 2.3.1 are affected by a reflected cross-site scripting flaw. The default GET handler in the GeneralHandler class prints query string input into an HTML page without sanitizing it, so a web server that extends this class without writing its own GET handler is exposed. An attacker can get a user to open a crafted link, which can run script in the victim's browser. No fix is listed; the source suggests implementing a custom GET handler in place of GeneralHandler's default.

Written 8 Nov 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

No source has published a CVSS score for this record yet.

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

## Timeline

- 31 Oct 2026, 15:12 UTC: First seen by agentprime
- 31 Oct 2026, 15:12 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-pr5m-4w22-8483)

## Sources

- [GitHub Advisory Database: GHSA-pr5m-4w22-8483](https://github.com/advisories/GHSA-pr5m-4w22-8483)
- [OSV: GHSA-pr5m-4w22-8483](https://osv.dev/vulnerability/GHSA-pr5m-4w22-8483)
- <https://nvd.nist.gov/vuln/detail/CVE-2020-13697>
- <https://github.com/NanoHttpd/nanohttpd>
- <https://github.com/NanoHttpd/nanohttpd/blob/efb2ebf85a2b06f7c508aba9eaad5377e3a01e81/nanolets/pom.xml>
- <https://github.com/NanoHttpd/nanohttpd/blob/efb2ebf85a2b06f7c508aba9eaad5377e3a01e81/nanolets/src/main/java/org/nanohttpd/router/RouterNanoHTTPD.java>
- <https://www.vdoo.com/advisories/#CVE-2020-13697>

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-pr5m-4w22-8483>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-pr5m-4w22-8483/>. Everything for agents: <https://agentprime.io/llms.txt>.
