Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-34215: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in parse-community parse-server

0
High
VulnerabilityCVE-2026-34215cvecve-2026-34215cwe-200
Published: Tue Mar 31 2026 (03/31/2026, 19:34:50 UTC)
Source: CVE Database V5
Vendor/Project: parse-community
Product: parse-server

Description

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.63 and 9.7.0-alpha.7, the verify password endpoint returns unsanitized authentication data, including MFA TOTP secrets, recovery codes, and OAuth access tokens. An attacker who knows a user's password can extract the MFA secret to generate valid MFA codes, defeating multi-factor authentication protection. This issue has been patched in versions 8.6.63 and 9.7.0-alpha.7.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/31/2026, 20:08:51 UTC

Technical Analysis

Parse Server is an open-source backend framework that runs on Node.js and is widely used for mobile and web application backends. CVE-2026-34215 is a vulnerability classified under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) that affects the verify password endpoint in parse-server versions prior to 8.6.63 and between 9.0.0 and 9.7.0-alpha.7. This endpoint improperly returns unsanitized authentication data, including multi-factor authentication (MFA) Time-based One-Time Password (TOTP) secrets, recovery codes, and OAuth access tokens. The vulnerability allows an attacker who already knows a user's password to retrieve these sensitive secrets, enabling them to generate valid MFA codes and bypass the multi-factor authentication protection. The vulnerability does not require user interaction and can be exploited remotely over the network without additional privileges beyond password knowledge. The issue has been addressed in parse-server versions 8.6.63 and 9.7.0-alpha.7 by sanitizing the response data to exclude sensitive authentication secrets. The CVSS 4.0 score is 8.2 (high), reflecting the network attack vector, low attack complexity, no privileges required beyond password knowledge, no user interaction, and high impact on confidentiality. No known exploits are currently reported in the wild, but the potential for account compromise is significant given the exposure of MFA secrets.

Potential Impact

The primary impact of this vulnerability is the compromise of multi-factor authentication, which is a critical security control for protecting user accounts. By exposing MFA TOTP secrets and recovery codes, attackers who have obtained user passwords can bypass MFA protections, leading to unauthorized access to user accounts and potentially sensitive data. This undermines the security posture of applications relying on parse-server for authentication and backend services. Organizations using affected versions risk account takeover, data breaches, and unauthorized access to protected resources. The exposure of OAuth access tokens further increases the risk by potentially allowing attackers to access third-party services or APIs linked via OAuth. The vulnerability affects confidentiality severely, with no direct impact on integrity or availability. The ease of exploitation (requiring only password knowledge) and the widespread use of parse-server in mobile and web applications globally amplify the threat's potential impact.

Mitigation Recommendations

Organizations should immediately upgrade parse-server to version 8.6.63 or later, or 9.7.0-alpha.7 or later, where the vulnerability has been patched. Until upgrades are applied, restrict access to the verify password endpoint by implementing network-level controls such as IP whitelisting or VPN access to reduce exposure. Review and audit user accounts for suspicious activity, especially those with known password leaks. Encourage users to change passwords and reset MFA configurations to invalidate potentially compromised secrets. Implement additional monitoring and alerting on authentication endpoints to detect abnormal access patterns. Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block attempts to exploit this endpoint. Finally, educate developers and administrators on secure handling of authentication data to prevent similar issues in future releases.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-26T15:57:52.324Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69cc2635e6bfc5ba1d36672c

Added to database: 3/31/2026, 7:53:25 PM

Last enriched: 3/31/2026, 8:08:51 PM

Last updated: 3/31/2026, 9:07:25 PM

Views: 2

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses