parse-server up to 7.5.2/8.2.1 GraphQL Schema information expsure

Summaryinfo

A vulnerability identified as problematic has been detected in parse-server up to 7.5.2/8.2.1. The affected element is an unknown function of the component GraphQL Schema Handler. This manipulation causes information expsure. This vulnerability appears as CVE-2025-53364. The attack may be initiated remotely. There is no available exploit. You should upgrade the affected component.

Detailsinfo

A vulnerability has been found in parse-server up to 7.5.2/8.2.1 and classified as problematic. Affected by this vulnerability is some unknown functionality of the component GraphQL Schema Handler. The manipulation with an unknown input leads to a information expsure vulnerability. The CWE definition for the vulnerability is CWE-497. The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does. As an impact it is known to affect confidentiality. The summary by CVE is:

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.

The weakness was presented by The Master. It is possible to read the advisory at github.com. This vulnerability is known as CVE-2025-53364 since 06/27/2025. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.

Upgrading to version 7.5.3 or 8.2.2 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-21001). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• parse-server

Version

• 7.5.0
• 7.5.1
• 7.5.2
• 8.2.0
• 8.2.1

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion