Information Disclosure in parse-server (CVE-2026-53725)
Summary
Vulnerability in parse-server (CVE-2026-53725). Risk of unauthorized operations or information disclosure. Exploitable via get. Mitigation: upgrade to 9.9.1-alpha.5 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-53725 has been found in parse-server.
Attackers can target a specific entry point like get over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade parse-server to 9.9.1-alpha.5 or later.
If unsure, ask your IT team or search "parse-server CVE-2026-53725" on the vendor's site.
CVE-2026-53725 (parse-server) — CWE-200
Attack surface: get / _User / protectedFields / authData
Patched: 9.9.1-alpha.5 — apply immediately
Workaround: None that preserve the intended _User get restriction.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in parse-server. Attackers reach the vulnerable code path via get.
Check the vendor advisory for the affected versions of parse-server. Attack surface: get / _User / protectedFields / authData.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 9.9.1-alpha.5.
Workaround: None that preserve the intended _User get restriction.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'parse-server' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'parse-server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
parse-serverを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
None that preserve the intended `_User` `get` restriction.パッチが適用されるまでの応急処置として、None that preserve the intended
_Usergetrestriction. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade parse-server to 9.9.1-alpha.5ステージング環境で 9.9.1-alpha.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com