Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.9amended

TypeORM vulnerable to SQL injection via crafted request to repository.save or repository.update

CVE-2025-60542GHSA-q2pj-6v73-8rgj

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (typeorm 0.3.26), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm typeorm

    Affected
    < 0.3.26
    Fixed in
    0.3.26

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.9 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:L/SI:H/SA:L/E:P · score source
EPSS
  • CVE-2025-60542: 0.27% estimated exploitation activity in the next 30 days; percentile 18.44 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary SQL Injection vulnerability in TypeORM before 0.3.26 via crafted request to repository.save or repository.update due to the sqlstring call using stringifyObjects default to false. Details Vulnerable Code: Intended Payload (non-malicious): username=myusername&city=Riga&name=Javad OR {username:\"myusername\",phone:12345,name:\"Javad\"} SQL query produced: Malicious Payload: username=myusername&city[name]=Riga&city[role]=admin OR {username:\"myusername\",city:{name:\"Javad\",role:\"admin\"}} SQL query produced with Injected Column: Above query is valid as city = name = Javad is a boolean expression resulting in city = 1 (false). “role” column is injected and updated. Underlying issue was due to TypeORM using mysql2 without specifying a value for the stringifyObjects option. In both mysql and mysql2 this option defaults to false. This option is then passed into SQLString library as false. This results in sqlstring parsing objects in a strange way using objectToValues.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-q2pj-6v73-8rgj

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-q2pj-6v73-8rgj

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-60542

Advisory: TypeORM vulnerable to SQL injection via crafted request to repository.save or repository.update
IDs: CVE-2025-60542, GHSA-q2pj-6v73-8rgj
Record: https://patchnext.com/advisories/cve-2025-60542 (revision 3, source checked 26 Oct 2026, 12:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: typeorm 0.3.26. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm typeorm: affected < 0.3.26; fixed in 0.3.26

## Suggested inspection (read-only)
- `npm ls typeorm --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on typeorm.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-q2pj-6v73-8rgj (OSV record GHSA-q2pj-6v73-8rgj lists affected ranges: npm typeorm >=0 <0.3.26 (fixed))
- Verified: https://github.com/advisories/GHSA-q2pj-6v73-8rgj (GitHub-reviewed advisory GHSA-q2pj-6v73-8rgj lists affected ranges: npm typeorm >=0 <0.3.26)

Commands are suggestions: review each one before running it.

Loading voting…