parse-server
Affected
- introduced
9.0.0-alpha.1, fixed9.6.0-alpha.5(semver)
Fixed versions
9.6.0-alpha.5
Fix
- Fixed version
9.6.0-alpha.5npm install [email protected]
Advisory
Also known as: BIT-parse-2026-31871, CVE-2026-31871
Parse Server vulnerable to SQL Injection via dot-notation sub-key name in Increment operation on PostgreSQL
Impact
A SQL injection vulnerability exists in the PostgreSQL storage adapter when processing Increment operations on nested object fields using dot notation (e.g., stats.counter). The sub-key name is interpolated directly into SQL string literals without escaping. An attacker who can send write requests to the Parse Server REST API can inject arbitrary SQL via a crafted sub-key name containing single quotes, potentially executing commands or reading data from the database, bypassing CLPs and ACLs.
Only Postgres deployments are affected.
Patches
The fix escapes single quotes in the sub-key name before interpolating it into the SQL query, preventing breakout from SQL string literals.
Workarounds
There is no known workaround.
References
Critical Basis: The source's own band: CRITICAL
9.0.0-alpha.1, fixed 9.6.0-alpha.5 (semver)9.6.0-alpha.5
9.6.0-alpha.5npm install [email protected]0, fixed 8.6.31 (semver)8.6.31
8.6.31npm 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