CVE-2026-80211

published 27 Aug 2026 · updated 24 Sep 2026

FrontAccounting through 2.4.20 Use of Unsalted MD5 for Password Storage

5.9MediumCVSS 5.9EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

FrontAccounting through 2.4.20 stores and verifies user passwords as unsalted MD5 digests. admin/users.php passes md5($_POST['password']) to add_user() and update_user_password(), admin/change_current_user_password.php does the same when a user changes their own password, the forgotten-password path in includes/current_user.inc hashes the newly generated password the same way, and authentication calls get_user_auth($loginname, md5($password)). The codebase applies no per-password salt and contains no call to password_hash(), password_verify() or any other adaptive hash, so identical passwords yield identical digests and an attacker who obtains the user table can recover plaintext passwords with precomputed lookup tables or high-rate GPU cracking.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
FrontAccounting<=2.4.20

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-80211 severity on Zeptric[![CVE-2026-80211](https://zeptric.io/badge/cve/CVE-2026-80211.svg)](https://zeptric.io/cve/CVE-2026-80211)