typeorm
Affected
- introduced
0, fixed0.3.26(semver)
Fixed versions
0.3.26
Fix
- Fixed version
0.3.26npm install [email protected]
Advisory
Also known as: CVE-2025-60542
TypeORM vulnerable to SQL injection via crafted request to repository.save or repository.update
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:
const { username, city, name} = req.body;
const updateData = {
username,
city,
name,
id:userId
}; // Developer aims to only allow above three fields to be updated
const result = await userRepo.save(updateData);
Intended Payload (non-malicious):
`
username=myusername&city=Riga&name=Javad
`
_OR_
`{username:\"myusername\",phone:12345,name:\"Javad\"}
`
SQL query produced:
UPDATE `user`
SET `username` = 'myusername',
`city` = 'Riga',
`name` = 'Javad'
WHERE `id` IN (1);
Malicious Payload:
`username=myusername&city[name]=Riga&city[role]=admin
`
_OR_
`{username:\"myusername\",city:{name:\"Javad\",role:\"admin\"}}
`
SQL query produced with Injected Column:
UPDATE `user`
SET `username` = 'myusername',
`city` = `name` = 'Javad',
`role` = 'admin'
WHERE `id` IN (1);
_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.
High Basis: The source's own band: HIGH
0, fixed 0.3.26 (semver)0.3.26
0.3.26npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0