Executive brief
Parse Server, an open-source backend framework, contains a flaw that allows unauthorized individuals to discover the internal structure of an application's database and custom functions. Even when security settings are enabled to hide this information, the system inadvertently reveals valid names through "Did you mean...?" suggestions in error messages. An attacker could use this information to map out a target's infrastructure, identifying hidden data tables and server-side functions to facilitate further attacks.
Technical details
A schema disclosure vulnerability exists in Parse Server's GraphQL API due to improper error handling during variable coercion. While the 'graphQLPublicIntrospection' setting (default: false) is intended to prevent schema discovery, the system still returns 'Did you mean...?' suggestions in error messages when a user provides near-miss enum values or input-object field names. This occurs because the existing introspection-hardening controls only applied to the validation phase, not the variable coercion phase. An unauthenticated remote attacker with only the public application ID can iteratively brute-force and recover hidden schema identifiers, including Cloud Code function names and Parse class/field names. This issue is a bypass of a previous fix (GHSA-8cph-rgr4-g5vj) and is resolved in versions 9.10.0-alpha.4 and 8.6.85.
Affected products
- Parse Community Parse Server >= 9.0.0, < 9.10.0-alpha.4; < 8.6.85
Timeline
- 2026-07-08: advisory: GitHub advisory published by maintainers
- 2026-07-21: disclosed: NVD publication date