CVE-2026-80211

FrontAccounting through 2.4.20 Use of Unsalted MD5 for Password Storage

Published Aug 27, 2026 CVSS 4.0 · 8.2 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

FrontAccounting versions up to 2.4.20 store and verify user passwords as unsalted MD5 digests. Because no salt is applied and the code does not use password_hash or password_verify, identical passwords produce identical digests, making it trivial for an attacker who obtains the user table to recover plaintext passwords with precomputed lookup tables or GPU‑accelerated cracking. This flaw directly undermines the confidentiality of user credentials and can enable unauthorized account access.

Affected Systems

The affected vendor is FrontAccounting: FrontAccounting. All releases up to and including version 2.4.20 are vulnerable. Users running FrontAccounting 2.4.20 or earlier must evaluate their installations for the presence of this weakness.

Risk and Exploitability

The CVSS score of 8.2 marks this as a high‑severity vulnerability. Although the EPSS score is not reported, the lack of a per‑password salt means that an attacker who gains database access can efficiently compromise all stored passwords. The vulnerability is not listed in the CISA KEV catalog, but the attack vector is likely a database compromise or insider access, after which the attacker can recover passwords before any mitigation is applied.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to FrontAccounting 2.4.21 or newer, which implements secure password hashing.
  • If an immediate upgrade is not possible, force all users to reset their passwords and store the new hashes with password_hash or a similar adaptive method.
  • Backup the user database before making any changes and monitor for suspicious activity.

Generated by OpenCVE AI on August 27, 2026 at 18:18 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

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

Type Values Removed Values Added
Description 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.
Title FrontAccounting through 2.4.20 Use of Unsalted MD5 for Password Storage
First Time appeared Frontaccounting
Frontaccounting frontaccounting
Weaknesses CWE-916
CPEs cpe:2.3:a:frontaccounting:frontaccounting:*:*:*:*:*:*:*:*
Vendors & Products Frontaccounting
Frontaccounting frontaccounting
References
Metrics cvssV3_1

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

cvssV4_0

{'score': 8.2, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-916

    Use of Password Hash With Insufficient Computational Effort

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Sep 24, 2026, 2:19 PM
Reserved
Aug 25, 2026, 11:15 PM
Status
Deferred
Published
Aug 27, 2026, 5:20 PM
Modified
Sep 23, 2026, 5:17 PM