parse-server
Affected
- introduced
9.0.0-alpha.1, fixed9.6.0-alpha.7(semver)
Fixed versions
9.6.0-alpha.7
Fix
- Fixed version
9.6.0-alpha.7npm install [email protected]
Advisory
Also known as: BIT-parse-2026-31875, CVE-2026-31875
Parse Server's MFA recovery codes not consumed after use
Impact
When multi-factor authentication (MFA) via TOTP is enabled for a user account, Parse Server generates two single-use recovery codes. These codes are intended as a fallback when the user cannot provide a TOTP token. However, recovery codes are not consumed after use, allowing the same recovery code to be used an unlimited number of times. This defeats the single-use design of recovery codes and weakens the security of MFA-protected accounts.
An attacker who obtains a single recovery code can repeatedly authenticate as the affected user without the code ever being invalidated.
Patches
The fix ensures that each recovery code is removed from the stored recovery code list after a successful login.
Workarounds
There is no known workaround.
References
High Basis: The source's own band: HIGH
9.0.0-alpha.1, fixed 9.6.0-alpha.7 (semver)9.6.0-alpha.7
9.6.0-alpha.7npm install [email protected]0, fixed 8.6.33 (semver)8.6.33
8.6.33npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0