CyberIntel ⬡ News
★ Saved ◆ Cyber Reads
← Back ⬡ Vulnerabilities & CVEs Mar 19, 2026

CVE-2026-33163 | parse-community parse-server up to 8.6.49/9.6.0-alpha.36 Personal Information toJSONwithObjects information disclosure (GHSA-5hmj-jcgp-6hff)

VulDB Archived Mar 19, 2026 ✓ Full text saved

A vulnerability described as problematic has been identified in parse-community parse-server up to 8.6.49/9.6.0-alpha.36 . The impacted element is the function toJSONwithObjects of the component Personal Information Handler . Executing a manipulation can lead to information disclosure. This vulnerability is tracked as CVE-2026-33163 . The attack can be launched remotely. No exploit exists. Upgrading the affected component is recommended.

Full text archived locally
✦ AI Summary · Claude Sonnet


    VDB-351623 · CVE-2026-33163 · GHSA-5HMJ-JCGP-6HFF PARSE-COMMUNITY PARSE-SERVER UP TO 8.6.49/9.6.0-ALPHA.36 PERSONAL INFORMATION TOJSONWITHOBJECTS INFORMATION DISCLOSURE HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.1 $0-$5k 1.30 Summaryinfo A vulnerability classified as problematic has been found in parse-community parse-server up to 8.6.49/9.6.0-alpha.36. This affects the function toJSONwithObjects of the component Personal Information Handler. The manipulation leads to information disclosure. This vulnerability is listed as CVE-2026-33163. The attack may be initiated remotely. There is no available exploit. It is recommended to upgrade the affected component. Detailsinfo A vulnerability, which was classified as problematic, has been found in parse-community parse-server up to 8.6.49/9.6.0-alpha.36. This issue affects the function toJSONwithObjects of the component Personal Information Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is: 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. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-33163 since 03/17/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK. Upgrading to version 8.6.50 or 9.6.0-alpha.35 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version. Productinfo Vendor parse-community Name parse-server Version 8.6.0 8.6.1 8.6.2 8.6.3 8.6.4 8.6.5 8.6.6 8.6.7 8.6.8 8.6.9 8.6.10 8.6.11 8.6.12 8.6.13 8.6.14 8.6.15 8.6.16 8.6.17 8.6.18 8.6.19 8.6.20 8.6.21 8.6.22 8.6.23 8.6.24 8.6.25 8.6.26 8.6.27 8.6.28 8.6.29 8.6.30 8.6.31 8.6.32 8.6.33 8.6.34 8.6.35 8.6.36 8.6.37 8.6.38 8.6.39 8.6.40 8.6.41 8.6.42 8.6.43 8.6.44 8.6.45 8.6.46 8.6.47 8.6.48 8.6.49 9.6.0-alpha.0 9.6.0-alpha.1 9.6.0-alpha.2 9.6.0-alpha.3 9.6.0-alpha.4 9.6.0-alpha.5 9.6.0-alpha.6 9.6.0-alpha.7 9.6.0-alpha.8 9.6.0-alpha.9 9.6.0-alpha.10 9.6.0-alpha.11 9.6.0-alpha.12 9.6.0-alpha.13 9.6.0-alpha.14 9.6.0-alpha.15 9.6.0-alpha.16 9.6.0-alpha.17 9.6.0-alpha.18 9.6.0-alpha.19 9.6.0-alpha.20 9.6.0-alpha.21 9.6.0-alpha.22 9.6.0-alpha.23 9.6.0-alpha.24 9.6.0-alpha.25 9.6.0-alpha.26 9.6.0-alpha.27 9.6.0-alpha.28 9.6.0-alpha.29 9.6.0-alpha.30 9.6.0-alpha.31 9.6.0-alpha.32 9.6.0-alpha.33 9.6.0-alpha.34 9.6.0-alpha.35 9.6.0-alpha.36 Website Product: https://github.com/parse-community/parse-server/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 5.3 VulDB Meta Temp Score: 5.1 VulDB Base Score: 5.3 VulDB Temp Score: 5.1 VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Information disclosure CWE: CWE-200 / CWE-284 / CWE-266 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: parse-server 8.6.50/9.6.0-alpha.35 Patch: github.com Timelineinfo 03/17/2026 CVE reserved 03/18/2026 +1 days Advisory disclosed 03/18/2026 +0 days VulDB entry created 03/18/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: GHSA-5hmj-jcgp-6hff Status: Confirmed CVE: CVE-2026-33163 (🔒) GCVE (CVE): GCVE-0-2026-33163 GCVE (VulDB): GCVE-100-351623 Entryinfo Created: 03/18/2026 23:57 Changes: 03/18/2026 23:57 (70) Complete: 🔍 Cache ID: 99:4E6:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸
    💬 Team Notes
    Article Info
    Source
    VulDB
    Category
    ⬡ Vulnerabilities & CVEs
    Published
    Mar 19, 2026
    Archived
    Mar 19, 2026
    Full Text
    ✓ Saved locally
    Open Original ↗