CVE-2025-32020
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 · uneditedThe crud-query-parser library parses query parameters from HTTP requests and converts them to database queries. Improper neutralization of the order/sort parameter in the TypeORM adapter, which allows SQL injection. You are impacted by this vulnerability if you are using the TypeORM adapter, ordering is enabled and you have not set-up a property filter. This vulnerability is fixed in 0.1.0.
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 crud-query-parser library contains a SQL injection vulnerability in its TypeORM adapter. The order/sort parameter from HTTP requests is not properly neutralized before being used in database queries, allowing attackers to inject malicious SQL when ordering is enabled and no property filter is configured.
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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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.
-
Identify crud-query-parser versionCheck your project's dependency manifest (package.json, requirements.txt, or equivalent) for the crud-query-parser package version, or run a package manager command to list installed versionAffected if The installed version is below 0.1.0 or the version cannot be determined (older installation)
-
Confirm TypeORM adapter usageInspect your application code to determine whether the TypeORM adapter from crud-query-parser is being used for database operationsAffected if The TypeORM adapter is in use as the data access layer
-
Verify ordering is enabledExamine the crud-query-parser configuration or initialization code for the ordering/sort feature flag or parameter (look for options like enableOrderBy, sortEnabled, or similar)Affected if Ordering functionality is explicitly enabled or allowed by default in the configuration
-
Check for property filter configurationReview the crud-query-parser setup to see if a property filter is defined to restrict which model properties can be used in order/sort operations (commonly configured via allowedProperties, whiteList, or propertyFilter options)Affected if No property filter is configured, meaning any model property can be used in the order/sort parameter
Your environment is affected if you have crud-query-parser below version 0.1.0, use the TypeORM adapter, have ordering enabled, and lack a property filter to constrain which properties can be used for sorting.
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.
dbcve · scopedUpgrade to version 0.1.0 or later. If upgrading is not immediately possible, ensure a property filter is configured to restrict which properties can be used in order/sort parameters.
0.1.0
- Check your project's dependency version for crud-query-parser (e.g., run npm list crud-query-parser or check package.json)
- Update crud-query-parser to version 0.1.0 or later using your package manager (npm update crud-query-parser or yarn upgrade crud-query-parser)
- Verify the new version is installed correctly
- Test the TypeORM adapter's order/sort functionality to confirm the SQL injection vulnerability is mitigated
- Ensure a property filter is configured for the order/sort parameter as an additional defense-in-depth measure (refer to library documentation)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32020 — 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-32020 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