ghsa-48q3-prgv-gm4w
Vulnerability from github
Published
2025-07-10 16:50
Modified
2025-07-10 19:22
Severity ?
VLAI Severity ?
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
{ "affected": [ { "package": { "ecosystem": "npm", "name": "parse-server" }, "ranges": [ { "events": [ { "introduced": "8.0.0" }, { "fixed": "8.2.2" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "npm", "name": "parse-server" }, "ranges": [ { "events": [ { "introduced": "5.3.0" }, { "fixed": "7.5.3" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2025-53364" ], "database_specific": { "cwe_ids": [ "CWE-497" ], "github_reviewed": true, "github_reviewed_at": "2025-07-10T16:50:36Z", "nvd_published_at": "2025-07-10T16:15:24Z", "severity": "MODERATE" }, "details": "### Impact\n\nThe 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.\n\n### Patches\n\nThe 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.\n\n### Workarounds\n\nNone available.\n\n### References\n\n- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-48q3-prgv-gm4w\n- Fix for Parse Server 7: https://github.com/parse-community/parse-server/pull/9820\n- Fix for Parse Server 8: https://github.com/parse-community/parse-server/pull/9819", "id": "GHSA-48q3-prgv-gm4w", "modified": "2025-07-10T19:22:40Z", "published": "2025-07-10T16:50:36Z", "references": [ { "type": "WEB", "url": "https://github.com/parse-community/parse-server/security/advisories/GHSA-48q3-prgv-gm4w" }, { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-53364" }, { "type": "WEB", "url": "https://github.com/parse-community/parse-server/pull/9819" }, { "type": "WEB", "url": "https://github.com/parse-community/parse-server/pull/9820" }, { "type": "PACKAGE", "url": "https://github.com/parse-community/parse-server" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N", "type": "CVSS_V3" } ], "summary": "Parse Server exposes the data schema via GraphQL API" }
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…