CVE-2025-64502
BaseFortify
Publication date: 2025-11-10
Last updated on: 2025-11-12
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| parse | parse_server | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in Parse Server allows any client to execute MongoDB explain() queries without requiring the master key prior to version 8.5.0-alpha.5. The explain() method reveals detailed information about database query execution plans, including schema structure, field names, index configurations, query optimization details, and performance metrics. This exposure can provide attackers with insights to exploit database performance or structure.
How can this vulnerability impact me? :
The vulnerability can expose sensitive database schema details and query performance information to unauthorized clients. This can lead to potential exploitation of database performance, unauthorized data inference, and increased risk of targeted attacks on the database infrastructure.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring and alerting on the usage of explain queries in your Parse Server environment, especially those executed without the master key. Since the vulnerability involves unauthorized explain queries revealing database details, you should look for explain query requests in your server logs or network traffic. There are no specific commands provided, but implementing middleware to log or block explain queries from non-master-key requests is recommended.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include configuring the new databaseOptions.allowPublicExplain option to restrict explain queries to requests authenticated with the master key. Although this option currently defaults to true, explicitly setting it to false will prevent public explain queries. Additionally, implement middleware to block explain queries from non-master-key requests and monitor explain query usage to detect potential exploitation.