Skip to content
Fencer Intel
medium 5.3

CVE-2025-53364 json

Parse Server exposes the data schema via GraphQL API

published last yr. modified 4mo ago also BIT-parse-2025-53364 , EUVD-2025-21001 , GHSA-48q3-prgv-gm4w

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 61%
public exploits
0
none known, plus a Nuclei check

Summary

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.

Patch / fix

  • npm parse-server 7.5.3, 8.2.2
  • bitnami parse 8.2.2
  • parseplatform parse-server 7.5.3, 8.2.2
  • parseplatform parse_server 7.5.3, 8.2.2

Is CVE-2025-53364 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.96% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Nuclei template Parse Server - GraphQL Schema Information Disclosure nuclei detection template

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
OSV 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
npm parse-server
>=8.0.0, <8.2.2
>=5.3.0, <7.5.3
8.2.2
7.5.3
bitnami parse
>=5.3.0, <8.2.2
8.2.2

Affected products

  • parse-community parse-server

Classification

Weakness
  • CWE-497 Exposure of Sensitive System Information to an Unauthorized Control Sphere

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.