CVE-2025-53364

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

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.

CVE-2025-53364 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (8.2.2, 7.5.3); upgrading removes the vulnerable code path.

Kodem intelligence

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.

1. What is CVE-2025-53364? CVE-2025-53364 is a medium-severity security vulnerability in parse-server (npm), affecting versions >= 8.0.0, < 8.2.2. It is fixed in 8.2.2, 7.5.3.
2. How severe is CVE-2025-53364? CVE-2025-53364 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of parse-server are affected by CVE-2025-53364? parse-server (npm) versions >= 8.0.0, < 8.2.2 is affected.
4. Is there a fix for CVE-2025-53364? Yes. CVE-2025-53364 is fixed in 8.2.2, 7.5.3. Upgrade to this version or later.
5. Is CVE-2025-53364 exploitable, and should I be worried? Whether CVE-2025-53364 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-53364 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-53364?
   • Upgrade parse-server to 8.2.2 or later
   • Upgrade parse-server to 7.5.3 or later