Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

npm package

crud-query-parser

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.6npmAmendedPublished

    crud-query-parser SQL Injection vulnerability

    CVE-2025-32020 · GHSA-9r25-rp3p-h2w4

    Affected
    • npm crud-query-parser < 0.1.0
    Fixed in
    0.1.0· Vendor fix available
    Issue
    Impact 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. Versions 0.0.1, 0.0.2 and 0.0.3 are affected by this vulnerability. Patches This vulnerability has been fixed in version 0.1.0 and newer, which introduces TypeORM field validation (enabled by default). Workarounds Add an allowlist of fields List all valid fields and use the filterProperties function to filter out invalid fields before passing the crudRequest to the TypeOrmQueryAdapter. Here's an example: Disable ordering Cleanup the order field just before passing it to the TypeOrmQueryAdapter. Here's an example:

    Recommended action: Upgrade to 0.1.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →