Advisory

GHSA-48q3-prgv-gm4w

Also known as: BIT-parse-2025-53364, CVE-2025-53364

Summary

Parse Server exposes the data schema via GraphQL API

Details

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

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2025-07-10 16:50 UTC
Modified
2025-07-16 09:57 UTC

Affected packages and fixes

parse-server

npm · All systems

Affected

  • introduced 8.0.0, fixed 8.2.2 (semver)

Fixed versions

8.2.2

Fix

parse-server

npm · All systems

Affected

  • introduced 5.3.0, fixed 7.5.3 (semver)

Fixed versions

7.5.3

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences