parse-server
Affected
- introduced
9.0.0, fixed9.6.0-alpha.10(semver)
Fixed versions
9.6.0-alpha.10
Fix
- Fixed version
9.6.0-alpha.10npm install [email protected]
Advisory
Also known as: BIT-parse-2026-32234, CVE-2026-32234
Parse Server has a SQL injection via query field name when using PostgreSQL
Impact
An attacker with access to the master key can inject malicious SQL via crafted field names used in query constraints when Parse Server is configured with PostgreSQL as the database. The field name in a $regex query operator is passed to PostgreSQL using unparameterized string interpolation, allowing the attacker to manipulate the SQL query. While the master key controls what can be done through the Parse Server abstraction layer, this SQL injection bypasses Parse Server entirely and operates at the database level.
This vulnerability only affects Parse Server deployments using PostgreSQL.
Patches
The fix applies proper SQL identifier escaping to field names in the query handler and hardens query field name validation to reject malicious field names for all query types.
Workarounds
There is no known workaround.
References
Medium Basis: The source's own band: MODERATE
9.0.0, fixed 9.6.0-alpha.10 (semver)9.6.0-alpha.10
9.6.0-alpha.10npm install [email protected]0, fixed 8.6.36 (semver)8.6.36
8.6.36npm 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