# CVE-2025-64502: Parse Server allows public `explain` queries which may expose sensitive database performance information and schema details

> Parse Server allows public explain queries, exposing database schema and performance details to unauthenticated attackers.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Nov 2025
- **Updated:** 12 Nov 2025
- **Also known as:** BIT-parse-2025-64502, GHSA-7cx5-254x-cgrq

## What is CVE-2025-64502?

CVE-2025-64502 is a medium-severity vulnerability in parse-community parse-server, published on 10 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. The MongoDB `explain()` method provides detailed information about query execution plans, including index usage, collection scanning behavior, and performance metrics. Prior to version 8.5.0-alpha.5, Parse Server permits any client to execute explain queries without requiring the master key. This exposes database schema structure and field names, index configurations and query optimization details, query execution statistics and performance metrics, and potential attack vectors for database performance exploitation. In version 8.5.0-alpha.5, a new `databaseOptions.allowPublicExplain` configuration option has been introduced that allows to restrict `explain` queries to the master key. The option defaults to `true` for now to avoid a breaking change in production systems that depends on public `explain` availability. In addition, a security warning is logged when the option is not explicitly set, or set to `true`. In a future major release of Parse Server, the default will change to `false`. As a workaround, implement middleware to block explain queries from non-master-key requests, or monitor and alert on explain query usage in production environments.

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)

## Which versions are affected by CVE-2025-64502?

3 open source packages ship an affected version, including parse-server and parse.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `parse-server` | npm | All versions | 8.5.0-alpha.5 |
| `parse-server` | npm | All versions | 8.5.0-alpha.5 |
| `parse` | Bitnami | All versions | 8.5.0 |

## How do I fix CVE-2025-64502?

Upgrade parse-server to 8.5.0-alpha.5 or later.

## Is CVE-2025-64502 being exploited?

There is no known exploitation of CVE-2025-64502 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-64502 and fix it if it is affected.

What it is: CVE-2025-64502 is a medium-severity vulnerability in parse-community parse-server, published on 10 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-64502 in the wild and no public exploit code.

Affected packages and fixed versions:
- parse-server (npm): affected all versions; fixed in 8.5.0-alpha.5
- parse-server (npm): affected all versions; fixed in 8.5.0-alpha.5
- parse (Bitnami): affected all versions; fixed in 8.5.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-64502/ (Markdown: https://insights.sbomify.com/CVE-2025-64502/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-64502
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-64502
- OSV: https://osv.dev/vulnerability/CVE-2025-64502

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-64502/
Summaries are generated and may contain mistakes; the official description above is the record.