parse-server
Affected
- introduced
9.0.0, fixed9.6.0-alpha.35(semver)
Fixed versions
9.6.0-alpha.35
Fix
- Fixed version
9.6.0-alpha.35npm install [email protected]
Advisory
Also known as: BIT-parse-2026-33163, CVE-2026-33163
Parse Server leaks protected fields via LiveQuery afterEvent trigger
Impact
When a Parse.Cloud.afterLiveQueryEvent trigger is registered for a class, the LiveQuery server leaks protected fields and authData to all subscribers of that class. Fields configured as protected via Class-Level Permissions (protectedFields) are included in LiveQuery event payloads for all event types (create, update, delete, enter, leave).
Any user with sufficient CLP permissions to subscribe to the affected class can receive protected field data of other users, including sensitive personal information and OAuth tokens from third-party authentication providers.
Patches
The vulnerability was caused by a reference detachment bug. When an afterEvent trigger is registered, the LiveQuery server converts the event object to a Parse.Object for the trigger, then creates a new JSON copy via toJSONwithObjects(). The sensitive data filter was applied to the Parse.Object reference, but the unfiltered JSON copy was sent to clients. The fix ensures that the JSON copy is assigned back to the response object before filtering, so the filter operates on the actual data sent to clients.
Workarounds
Remove all Parse.Cloud.afterLiveQueryEvent trigger registrations. Without an afterEvent trigger, the reference detachment does not occur and protected fields are correctly filtered.
High Basis: The source's own band: HIGH
9.0.0, fixed 9.6.0-alpha.35 (semver)9.6.0-alpha.35
9.6.0-alpha.35npm install [email protected]0, fixed 8.6.50 (semver)8.6.50
8.6.50npm 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