dbcve.org
Next.jsApplication · Zeit

CVE-2018-18282

MEDIUM · 6.1 CVSS v3.0 Published 2018-10-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Next.js versions 7.0.0 and 7.0.1 contain a cross-site scripting (XSS) vulnerability in the built-in error pages (/404 and /500 accessed via /_error). User-supplied input rendered on these error pages is not properly sanitized, allowing injection of malicious scripts.

MitigationUpgrade Next.js to version 7.0.2 or later where this XSS vulnerability in the error pages has been patched.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Next.jsApplication
Affected:= 7.0.0= 7.0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Next.js installation and version
    Run 'npm list next' or check the 'next' dependency version in your package.json file
    Affected if The installed version is 7.0.0 or 7.0.1
  2. Locate the Next.js package directory
    Find the node_modules/next directory and run 'cat node_modules/next/package.json | grep version' to confirm the installed version
    Affected if The version listed is exactly 7.0.0 or 7.0.1
  3. Determine if default error pages are in use
    Check if custom error pages exist at pages/_error.js, pages/404.js, or pages/500.js in your project. If these files do not exist, the built-in error pages are being used.
    Affected if No custom error page components exist in the pages directory, meaning the vulnerable built-in error pages are active
  4. Test error page for XSS injection
    Access /_error?message=<script>alert(1)</script> or /404?status=500&message=<img+src=x+onerror=alert(1)> and inspect the rendered HTML to see if the input is reflected without sanitization
    Affected if The injected script or HTML tags appear unescaped in the page source, confirming the XSS vulnerability is exploitable

You are affected if Next.js version 7.0.0 or 7.0.1 is installed and the built-in error pages (/_error, /404, /500) are being used without custom error page components.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Next.js to version 7.0.2 or later where this XSS vulnerability in the error pages has been patched.

Fix this in Next.js Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-18282 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-18282 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data