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.
Published: 2026-09-24
Score: 5.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Authentication degradation via single-factor
Action: Patch
AI Analysis

Impact

Termix’s 2.4.0 through 2.5.1 releases allowed the POST /users/totp/disable and POST /users/totp/backup-codes endpoints to accept the account password alone as a reauthentication factor. The code treated the password and the TOTP code as interchangeable credentials, so an attacker who has an authenticated session and knows the victim’s password could disable TOTP or regenerate backup codes without a valid second factor, effectively reducing the account to single‑factor authentication.

Affected Systems

The affected product is Termix by Termix-SSH. Versions from 2.4.0 up to and including 2.5.1 are vulnerable; the issue is remedied in 2.5.1 and later.

Risk and Exploitability

The CVSS score of 5.3 reflects a moderate severity. EPSS is not available, and the vulnerability is not listed in CISA’s KEV catalog. Based on the description, the likely attack vector is over the web application; an attacker must already have a valid session and the victim’s password. Once the conditions are met, disabling TOTP or invalidating backup codes can be performed via the vulnerable HTTP POST endpoints, weakening the account to single‑factor authentication.

Generated by OpenCVE AI on September 25, 2026 at 06:27 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Termix to version 2.5.1 or later to enforce two‑factor reauthentication on the affected endpoints
  • Re‑generate TOTP configurations and refresh backup codes for accounts that may have been compromised
  • Monitor account activity for unauthorized TOTP disabling or backup code regeneration

Generated by OpenCVE AI on September 25, 2026 at 06:27 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 25 Sep 2026 14:45:00 +0000

Type Values Removed Values Added
First Time appeared Termix
Termix termix
Vendors & Products Termix
Termix termix

Thu, 24 Sep 2026 18:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Thu, 24 Sep 2026 16:30:00 +0000

Type Values Removed Values Added
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.
Title Termix: MFA-critical operations accept the account password as a sole factor (regression of CVE-2026-45749)
Weaknesses CWE-308
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-09-24T17:09:04.634Z

Reserved: 2026-08-25T14:08:18.111Z

Link: CVE-2026-79763

cve-icon Vulnrichment

Updated: 2026-09-24T17:08:53.231Z

cve-icon NVD

Status : Deferred

Published: 2026-09-24T17:17:06.370

Modified: 2026-09-24T19:39:45.600

Link: CVE-2026-79763

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-25T14:17:07Z

Weaknesses
  • CWE-308

    Use of Single-factor Authentication