Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2026-33163— Parse Server leaks protected fields via LiveQuery afterEvent trigger

EPSS 0.03% · P9
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2026-33163

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Parse Server leaks protected fields via LiveQuery afterEvent trigger
Source: NVD (National Vulnerability Database)
Vulnerability Description
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.6.0-alpha.35 and 8.6.50, 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. 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 in versions 9.6.0-alpha.35 and 8.6.50 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. As a workaround, remove all `Parse.Cloud.afterLiveQueryEvent` trigger registrations. Without an `afterEvent` trigger, the reference detachment does not occur and protected fields are correctly filtered.
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
信息暴露
Source: NVD (National Vulnerability Database)
Vulnerability Title
Parse Server 信息泄露漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Parse Server是Parse Platform开源的一个开源后端,可以部署到任何可以运行 Node.js 的基础设施。 Parse Server 9.6.0-alpha.35之前版本和8.6.50之前版本存在信息泄露漏洞,该漏洞源于LiveQuery服务器泄露受保护字段,可能导致敏感信息泄露。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
parse-communityparse-server >= 9.0.0, < 9.6.0-alpha.35 -

II. Public POCs for CVE-2026-33163

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-33163

登录查看更多情报信息。

Same Patch Batch · parse-community · 2026-03-18 · 9 CVEs total

CVE-2026-327705.9 MEDIUMParse Server: LiveQuery subscription with invalid regular expression crashes server
CVE-2026-327424.3 MEDIUMParse Server session creation endpoint allows overwriting server-generated session fields
CVE-2026-32886Parse Server's Cloud function dispatch crashes server via prototype chain traversal
CVE-2026-32728Parse Server has a stored XSS filter bypass via Content-Type MIME parameter and missing XM
CVE-2026-32878Parse Server vulnerable to schema poisoning via prototype pollution in deep copy
CVE-2026-32944Parse Server crash via deeply nested query condition operators
CVE-2026-32943Parse Server has a password reset token single-use bypass via concurrent requests
CVE-2026-33042Parse Server affected by empty authData bypassing credential requirement on signup

IV. Related Vulnerabilities

V. Comments for CVE-2026-33163

No comments yet


Leave a comment