Termix: MFA-critical operations accept the account password as a sole factor (regression of CVE-2026-45749)
What fixes it
No source in this snapshot names a fixed version. The vendor advisories under References are the place to check.
Description
Termix is a web-based server management platform with SSH terminal, tunneling, and file editing capabilities. From 2.4.0 until 2.5.1, the POST /users/totp/disable and POST /users/totp/backup-codes endpoints accept the account password as the sole reauthentication factor after a 2.4.0 refactor regressed the two-factor check introduced for CVE-2026-45749. In src/backend/database/routes/user-totp-routes.ts, verifyTotpReauth returns success when bcrypt.compare validates the password, while each endpoint chooses password or totp_code as an interchangeable credential. An attacker who has a victim's authenticated session and knows the password can disable TOTP or regenerate and invalidate backup codes without an authenticator or valid second factor, weakening the account to single-factor authentication. This issue is fixed in version 2.5.1.
Text from CVE List
Affected versions 1
- Termixaffected: >= 2.4.0, < 2.5.1CVE List
References 5
- github.com/Termix-SSH/Termix/commit/22124e1bc49c8cedad57b31de9c51ad39f3d4432Fixvia CVE List
- github.com/Termix-SSH/Termix/commit/ddbdd5c437c2296607dfaa4265d6f63fbc1ca92eFixvia CVE List
- github.com/Termix-SSH/Termix/releases/tag/release-2.5.1-tagFixvia CVE List
- github.com/Termix-SSH/Termix/security/advisories/GHSA-x9h9-f7jc-8jwjExploitvia CVE List
- github.com/Termix-SSH/Termix/pull/1067Referencevia CVE List