parse-server up to 8.4.0-alpha.1 explain insertion of sensitive information into sent data
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in parse-server. This issue affects the function explain. Executing a manipulation can lead to insertion of sensitive information into sent data.
This vulnerability is handled as CVE-2025-64502. The attack can be executed remotely. There is not any exploit available.
Upgrading the affected component is advised.
Details
A vulnerability classified as problematic was found in parse-server. This vulnerability affects the function explain. The manipulation with an unknown input leads to a insertion of sensitive information into sent data vulnerability. The CWE definition for the vulnerability is CWE-201. The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor. As an impact it is known to affect confidentiality. CVE summarizes:
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.
The weakness was released by The Master as GHSA-7cx5-254x-cgrq. The advisory is available at github.com. This vulnerability was named CVE-2025-64502 since 11/05/2025. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1592 by the MITRE ATT&CK project.
Upgrading to version 8.5.0-alpha.5 eliminates this vulnerability. Applying the patch 4456b02280c2d8dd58b7250e9e67f1a8647b3452 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
- 3.4.1
- 3.6.0
- 4.1.3
- 4.5.0
- 4.10.18
- 5.3.0
- 5.3.1
- 5.4.1
- 6.5.0
- 6.5.5
- 6.5.7
- 6.5.9
- 7.0.0-alpha.19
- 7.0.0-alpha.20
- 7.0.0-alpha.28
- 7.0.0-alpha.29
- 7.1.0
- 7.2
- 7.3.0
- 7.5.2
- 7.5.3
- 7.5.4
- 8.0.1
- 8.0.2
- 8.2.1
- 8.2.2
- 8.4.0-alpha.1
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Insertion of sensitive information into sent dataCWE: CWE-201 / CWE-200 / CWE-284
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: parse-server 8.5.0-alpha.5
Patch: 4456b02280c2d8dd58b7250e9e67f1a8647b3452
Timeline
11/05/2025 CVE reserved11/11/2025 Advisory disclosed
11/11/2025 VulDB entry created
11/11/2025 VulDB entry last update
Sources
Advisory: GHSA-7cx5-254x-cgrqResearcher: The Master
Status: Confirmed
CVE: CVE-2025-64502 (🔒)
GCVE (CVE): GCVE-0-2025-64502
GCVE (VulDB): GCVE-100-331786
Entry
Created: 11/11/2025 07:30Changes: 11/11/2025 07:30 (69)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.