1. Home
  2. Vulnerabilities
  3. CVE-2025-60542
0.0
NA
CVE-2025-60542
TypeORM SQL Injection
Description

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.

INFO

Published Date :

Oct. 29, 2025, 4:15 p.m.

Last Modified :

Oct. 29, 2025, 4:15 p.m.

Remotely Exploit :

No

Source :

[email protected]
Affected Products

The following products are affected by CVE-2025-60542 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

: Total Affected Vendor : 0 | Products : 0
Solution
Update TypeORM to version 0.3.26 or later to fix SQL injection.
  • Update TypeORM to version 0.3.26 or later.
  • Review and sanitize all user inputs.
  • Ensure stringifyObjects is set to true if applicable.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2025-60542.

URL Resource
https://github.com/typeorm/typeorm/pull/11574
https://github.com/typeorm/typeorm/releases/tag/0.3.26
https://github.com/typeorm/typeorm/releases?q=security&expanded=true
https://medium.com/@alizada.cavad/cve-2025-60542-typeorm-mysql-sqli-0-3-25-a1b32bc60453
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2025-60542 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2025-60542 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2025-60542 vulnerability anywhere in the article.

Results are limited to the first 20 news articles due to potential performance issues.

The following table lists the changes that have been made to the CVE-2025-60542 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by [email protected]

    Oct. 29, 2025

    Action Type Old Value New Value
    Added Description 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.
    Added Reference https://github.com/typeorm/typeorm/pull/11574
    Added Reference https://github.com/typeorm/typeorm/releases/tag/0.3.26
    Added Reference https://github.com/typeorm/typeorm/releases?q=security&expanded=true
    Added Reference https://medium.com/@alizada.cavad/cve-2025-60542-typeorm-mysql-sqli-0-3-25-a1b32bc60453
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
No CVSS metrics available for this vulnerability.