All vulnerabilities

Servers and applications

GHSA-57wv-g7m3-hmff

Password change does not invalidate existing panel sessions, API keys, or 2FA trust cookies

Severity
Medium
Published
6 Sept 2026
Last changed
6 Sept 2026
Added to UpHeron
1 Nov 2026
Fixed in
2.3.12
Weakness
Insufficient session expiration (CWE-613)
Sources
Project advisories (GitHub)

Description

Changing a user's password — the standard incident-response action after credential compromise — invalidates nothing else in froxlor: existing panel sessions stay logged in, API keys keep working, and 2FA "remember this device" tokens survive. An attacker holding any of these artifacts retains access after the password rotation, up to admin level.

The password-update paths write only the password column:

Repo-wide, session_destroy() exists only at explicit logout (admin_index.php:49, customer_index.php:50); panel authentication trusts $_SESSION['userinfo'], which is password-independent. api_keys rows are invalidated only on account deactivation or deletion (Customers.php:1455-1461, :1885) — never on password change. The frx_2fa_remember trust cookie (index.php:120-145) is backed by panel_2fa_tokens, purged only by cron expiry (Cli/MasterCron.php:185) — not on password change or 2FA reset.

From froxlor/froxlor's security advisory. Shortened; the full text is there.

Affected software

SoftwareAffected versions
FroxlorServers and applications · github:froxlor/froxlor
  • Every version before 2.3.12

About Froxlor

The server administration software for your needs - The official Froxlor development Git repository

From its GitHub repository.
Monthly downloads (Packagist)
159Packagist, 15 Nov 2026
Total downloads (Packagist)
406Packagist, 15 Nov 2026
GitHub stars
1,752GitHub, 15 Nov 2026
Forks
467GitHub, 15 Nov 2026
Latest release
2.3.17GitHub, 15 Nov 2026
Released
8 Nov 2026GitHub
License
GNU Lesser General Public License, version 2.1Wikidata
Written in
PHPWikidata
First published on GitHub
6 Mar 2012GitHub

References