CVE-2026-53725: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in parse-community parse-server
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. From version 9.8.0 to before version 9.9.1-alpha.5, apps that enable MFA and deny get on the _User class via Class-Level Permissions could expose sensitive user data through the /login and /verifyPassword endpoints. These endpoints re-fetch the user through the access-controlled query pipeline (CLP, protectedFields, auth-adapter sanitizers) before responding. When that re-fetch was denied by the _User get permission, the server fell back to the raw database row, exposing raw authData (including MFA TOTP secrets and recovery codes) and fields hidden by protectedFields (when protectedFieldsOwnerExempt is false). /verifyPassword is the most severe: with only a username and password (no session or MFA token), an attacker who knows a victim's password could retrieve their MFA secret and recovery codes, defeating the second factor. This issue has been patched in version 9.9.1-alpha.5.
AI Analysis
Technical Summary
CVE-2026-53725 is a vulnerability in parse-community's parse-server affecting versions >=9.8.0 and <9.9.1-alpha.5. When MFA is enabled and get access on the _User class is denied via Class-Level Permissions, the /login and /verifyPassword endpoints improperly expose sensitive user data. The endpoints attempt to re-fetch the user through access-controlled queries, but if denied, the server falls back to returning the raw database row. This fallback exposes raw authData fields including MFA TOTP secrets and recovery codes, as well as fields protected by protectedFields when protectedFieldsOwnerExempt is false. The /verifyPassword endpoint is the most critical vector, as it allows an attacker who knows a victim's password to retrieve MFA secrets without requiring a session or MFA token, effectively defeating the second factor authentication. The issue was fixed in version 9.9.1-alpha.5.
Potential Impact
Sensitive user authentication data including MFA TOTP secrets and recovery codes can be exposed to unauthorized actors if they know a victim's username and password. This exposure can allow attackers to bypass multi-factor authentication protections, significantly weakening account security. The vulnerability affects the confidentiality of user credentials and MFA secrets.
Mitigation Recommendations
A fix is available in parse-server version 9.9.1-alpha.5. Users should upgrade to this version or later to remediate the vulnerability. No other mitigation guidance is provided by the vendor advisory. Patch status is not explicitly stated beyond the fixed version, so users should verify the upgrade and test accordingly.
CVE-2026-53725: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in parse-community parse-server
Description
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. From version 9.8.0 to before version 9.9.1-alpha.5, apps that enable MFA and deny get on the _User class via Class-Level Permissions could expose sensitive user data through the /login and /verifyPassword endpoints. These endpoints re-fetch the user through the access-controlled query pipeline (CLP, protectedFields, auth-adapter sanitizers) before responding. When that re-fetch was denied by the _User get permission, the server fell back to the raw database row, exposing raw authData (including MFA TOTP secrets and recovery codes) and fields hidden by protectedFields (when protectedFieldsOwnerExempt is false). /verifyPassword is the most severe: with only a username and password (no session or MFA token), an attacker who knows a victim's password could retrieve their MFA secret and recovery codes, defeating the second factor. This issue has been patched in version 9.9.1-alpha.5.
CVSS v4.0
Score 5.9medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-53725 is a vulnerability in parse-community's parse-server affecting versions >=9.8.0 and <9.9.1-alpha.5. When MFA is enabled and get access on the _User class is denied via Class-Level Permissions, the /login and /verifyPassword endpoints improperly expose sensitive user data. The endpoints attempt to re-fetch the user through access-controlled queries, but if denied, the server falls back to returning the raw database row. This fallback exposes raw authData fields including MFA TOTP secrets and recovery codes, as well as fields protected by protectedFields when protectedFieldsOwnerExempt is false. The /verifyPassword endpoint is the most critical vector, as it allows an attacker who knows a victim's password to retrieve MFA secrets without requiring a session or MFA token, effectively defeating the second factor authentication. The issue was fixed in version 9.9.1-alpha.5.
Potential Impact
Sensitive user authentication data including MFA TOTP secrets and recovery codes can be exposed to unauthorized actors if they know a victim's username and password. This exposure can allow attackers to bypass multi-factor authentication protections, significantly weakening account security. The vulnerability affects the confidentiality of user credentials and MFA secrets.
Mitigation Recommendations
A fix is available in parse-server version 9.9.1-alpha.5. Users should upgrade to this version or later to remediate the vulnerability. No other mitigation guidance is provided by the vendor advisory. Patch status is not explicitly stated beyond the fixed version, so users should verify the upgrade and test accordingly.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-10T16:43:31.242Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a2c5615e617e2d834b0f481
Added to database: 06/12/2026, 18:55:17 UTC
Last enriched: 06/14/2026, 20:02:38 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 99
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.