# CVE-2026-53725: parse-server: Endpoints `/login` and `/verifyPassword` disclose MFA secrets and protected fields when `_User` get is denied

> Attackers with valid credentials can retrieve MFA secrets and protected fields via login endpoints when user get permissions are denied, bypassing two-factor authentication.

- **Severity:** Medium 5.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Jun 2026
- **Updated:** 13 Jun 2026
- **Also known as:** BIT-parse-2026-53725, GHSA-75v4-m273-5j49

## What is CVE-2026-53725?

CVE-2026-53725 is a medium-severity vulnerability in parse-community parse-server, published on 12 Jun 2026. An attacker needs administrator access to exploit it, 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. 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-53725?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `parse-server` | npm | From 9.8.0 | 9.9.1-alpha.5 |
| `parse-server` | npm | From 9.8.0 | 9.9.1-alpha.5 |
| `parse` | Bitnami | From 9.8.0 | 9.9.1 |

## How do I fix CVE-2026-53725?

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

## Is CVE-2026-53725 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53725 and fix it if it is affected.

What it is: CVE-2026-53725 is a medium-severity vulnerability in parse-community parse-server, published on 12 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-53725 in the wild and no public exploit code.

Affected packages and fixed versions:
- parse-server (npm): affected from 9.8.0; fixed in 9.9.1-alpha.5
- parse-server (npm): affected from 9.8.0; fixed in 9.9.1-alpha.5
- parse (Bitnami): affected from 9.8.0; fixed in 9.9.1

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-2026-53725/ (Markdown: https://insights.sbomify.com/CVE-2026-53725/index.md)
```

## Sources

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

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