CVE-2025-63704
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 · uneditedNPM package query-parser-string 1.0.0 is vulnerable to Prototype Pollution. The package does not properly sanitize user supplied query parameters and merges them to the newly created object.
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 confidenceThe NPM package query-parser-string version 1.0.0 is vulnerable to Prototype Pollution due to improper sanitization of user-supplied query parameters. The package directly merges query parameters into a newly created object without filtering out dangerous property names like __proto__, constructor, or prototype, allowing attackers to modify Object.prototype and potentially execute arbitrary code.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Locate query-parser-string in dependenciesInspect your project is package.json file for 'query-parser-string' in the dependencies, devDependencies, or peerDependencies sections. Alternatively, run 'npm list query-parser-string' in the project root.Affected if The package is listed as a dependency in package.json or present in node_modules
-
Identify the installed versionRun 'npm list query-parser-string' or check the version field in node_modules/query-parser-string/package.json. Compare the version number to the affected range.Affected if The installed version is exactly 1.0.0 or falls within an unpatched version range
-
Find code that imports or uses the packageSearch your codebase for require('query-parser-string') or import statements referencing query-parser-string. Identify the functions being called and the variables being passed to them.Affected if The package is imported and its functions are invoked in your application code
-
Determine if user input reaches the vulnerable functionTrace the data flow from incoming HTTP request query parameters (req.query, request.params, or similar) to the query-parser-string function. Check if raw query string data is passed directly without prior validation.Affected if User-supplied query parameters from HTTP requests are passed directly to the package's parsing function
You are affected if your application uses query-parser-string version 1.0.0 and passes user-controlled query parameters to its parsing function without sanitization.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to a patched version of query-parser-string that implements proper input validation to reject or sanitize hazardous property names (__proto__, constructor, prototype) before merging query parameters into objects.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-63704 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-63704 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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