CVE-2025-53364: Parse Server exposes the data schema via GraphQL API
Impact
The Parse Server GraphQL API previously allowed public access to the GraphQL schema without requiring a session token or the master key. While schema introspection reveals only metadata and not actual data, this metadata can still expand the potential attack surface.
Patches
The issue has been addressed by requiring the master key for schema introspection. Additionally, a new Parse Server configuration option, graphQLPublicIntrospection, has been introduced. This option allows developers to re-enable public schema introspection if their application relies on it. However, it is strongly recommended to use this option only temporarily and to update the application to function without depending on public introspection.
Workarounds
None available.
References
- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-48q3-prgv-gm4w - Fix for Parse Server 7: https://github.com/parse-community/parse-server/pull/9820 - Fix for Parse Server 8: https://github.com/parse-community/parse-server/pull/9819
Other sources
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Starting in 5.3.0 and before 7.5.3 and 8.2.2, the Parse Server GraphQL API previously allowed public access to the GraphQL schema without requiring a session token or the master key. While schema introspection reveals only metadata and not actual data, this metadata can still expand the potential attack surface. This vulnerability is fixed in 7.5.3 and 8.2.2.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-53364?
CVE-2025-53364 is considered a moderate severity vulnerability due to its potential to expose sensitive GraphQL schema information.
How do I fix CVE-2025-53364?
To fix CVE-2025-53364, upgrade your Parse Server to version 7.5.3 or higher, or to version 8.2.2 or higher.
What versions of Parse Server are affected by CVE-2025-53364?
CVE-2025-53364 affects Parse Server versions from 5.3.0 to 7.5.3, and from 7.5.3 to 8.2.2.
What kind of exposure does CVE-2025-53364 present?
CVE-2025-53364 allows public access to the GraphQL schema without authentication, potentially leaking sensitive data.
Is there a workaround for CVE-2025-53364 if I cannot upgrade?
If unable to upgrade for CVE-2025-53364, implement authentication measures for the GraphQL API to restrict access.