VulnerabilityPublished 10 Jul 2025

CVE-2025-53364: parse-server · Exposure of Sensitive System Information to an Unauthorized Control Sphere

Affects parse-serverSource CVE Database V5

Not known to be exploited · public detection template (Nuclei) · CVSS 5.3 Medium : upgrade to 8.2.2 or 7.5.3 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.9% chance of exploitation in 30 days – higher than 61% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.2.2, 7.5.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Jul 2025
Detectable: evidence found.
nuclei template: Parse Server - GraphQL Schema Information Disclosure
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade parse-server to 8.2.2 or 7.5.3.

Affected software

Product	Affected	Fixed in
npmparse-server`pkg:npm/parse-server`Other threats	Affected >=5.3.0 <7.5.3 >=7.5.3 <8.2.2	Fixed in 7.5.3 8.2.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, European organizations should: 1) Immediately upgrade parse-server instances to version 7.5.3 or 8.2.2 or later, where the issue is fixed. 2) Review and restrict access controls on GraphQL endpoints to ensure that schema introspection is only accessible to authenticated and authorized users. 3) Implement network-level protections such as Web Application Firewalls (WAFs) to monitor and block unauthorized schema introspection requests. 4) Conduct thorough security assessments and penetration testing focused on GraphQL APIs to identify any additional weaknesses. 5) Monitor logs for unusual or repeated schema introspection queries from unknown or suspicious IP addresses. 6) Educate development and operations teams about the risks of exposing API metadata and enforce secure API design principles. 7) If immediate upgrade is not feasible, consider disabling GraphQL schema introspection or limiting it via custom middleware as a temporary workaround.

Description

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.

Impact

For European organizations, the exposure of GraphQL schema metadata could aid attackers in reconnaissance activities, enabling them to better understand backend data structures and API operations. This knowledge can be leveraged to craft more effective attacks, such as injection attacks, unauthorized data access attempts, or privilege escalation exploits. While no direct data leakage occurs from schema introspection alone, the increased attack surface can indirectly lead to breaches if combined with other vulnerabilities or misconfigurations. Organizations handling sensitive or regulated data (e.g., personal data under GDPR) may face compliance risks if this vulnerability is exploited as part of a broader attack chain. Furthermore, organizations relying on parse-server for critical business applications could experience reputational damage and operational disruption if attackers leverage this information to compromise systems. The medium severity indicates that while the immediate risk is moderate, the potential for escalation exists, especially in complex environments where multiple vulnerabilities coexist.

CWE-497Exposure of Sensitive System Information to an Unauthorized Control Sphere (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
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.
Architecture and Design · Implementation
Production applications should never use methods that generate internal details such as stack traces and error messages unless that information is directly committed to a log that is not viewable by the end user.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V14.3.2 (opens in a new tab)
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
Attack patterns
Web Application Fingerprinting (opens in a new tab)
System Location Discovery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Jul 2025, 15:46 UTC

Public exploits and detectiona Nuclei detection template

WeaknessesCWE-497

Technical details

References

Community reviews

Related threats