Sign in
Deutsch English Español Polski
Medium

Froxlor Information Disclosure

  • Disclosed: 24.05.2022
  • Updated: 11.10.2026 10:22

An issue was discovered in Froxlor before 0.10.14. It created files with static names in /tmp during installation if the installation directory was not writable. This allowed local attackers to cause DoS or disclose information out of the config files, because of _createUserdataConf in install/lib/class.FroxlorInstall.php.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Composer package froxlor/froxlor < 0.10.14 0.10.14

References

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

Sources and licenses

OSV / GitHub Advisory Database - GHSA-hvgf-2rf7-wrx9 - 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

Severity:
  1. Froxlor Information Disclosure this entry
    Medium · 6.1 CVE-2020-10236 < 0.10.14 0.10.14
  2. Froxlor: Credential and 2FA secret disclosure via Froxlor API endpoints
    Critical · 9.0 CVE-2026-62988 < 2.3.8 2.3.8
  3. Froxlor: Second-Order SQL Injection via `Admins.add` `ipaddress` Parameter Allows Full Database Exfiltration
    High · 7.2 CVE-2026-54348 < 2.3.8 2.3.8
  4. Froxlor: Stored XSS in DNS TXT Record Content Allows Customer-to-Admin Account Takeover
    High · 8.7 CVE-2026-54347 < 2.3.8 2.3.8
  5. Froxlor's API Authentication bypasses 2FA Authentication
    High · 8.1 CVE-2026-52793 < 2.3.7 2.3.7
  6. Froxlor: BIND Zone File Injection via TXT Record Content
    High · 7.6 CVE-2026-41234 < 2.3.7 2.3.7
  7. Froxlor has an incomplete fix for CVE-2026-30932
    High CVE-2026-41237 < 2.3.7 2.3.7
  8. Froxlor has privilege escalation in SSH key synchronization via symlinked `authorized_keys` path
    High · 8.8 CVE-2026-41236 >= 2.3.6, < 2.3.7 2.3.7
  9. Froxlor has an authorization bypass in FTP shell assignment via missing server-side `available_shells` enforcement
    High · 8.8 CVE-2026-41235 >= 2.3.6, < 2.3.7 2.3.7
  10. Froxlor has Local File Inclusion via path traversal in API `def_language` parameter leads to Remote Code Execution
    Critical · 9.9 CVE-2026-41228 < 2.3.6 2.3.6
  11. Froxlor has a PHP Code Injection via Unescaped Single Quotes in userdata.inc.php Generation (MysqlServer API)
    Critical · 9.1 CVE-2026-41229 < 2.3.6 2.3.6
  12. Froxlor has a BIND Zone File Injection via Unsanitized DNS Record Content in DomainZones::add()
    High · 8.5 CVE-2026-41230 < 2.3.6 2.3.6
  13. Froxlor has Incomplete Symlink Validation in DataDump.add() Allows Arbitrary Directory Ownership Takeover via Cron
    High · 7.5 CVE-2026-41231 < 2.3.6 2.3.6
  14. Froxlor is vulnerable to BIND zone file injection via unsanitized DNS record content in DomainZones API
    High · 8.8 CVE-2026-30932 < 2.3.5 2.3.5
  15. Froxlor has Admin-to-Root Privilege Escalation via Input Validation Bypass + OS Command Injection
    Critical · 9.1 CVE-2026-26279 < 2.3.4 2.3.4
  16. Froxlor: /etc/pure-ftpd/db/mysql.conf is chmod 644 but contains <SQL_UNPRIVILEGED_PASSWORD>
    High · 7.3 CVE-2024-58383 < 2.2.0 2.2.0
  17. Blind XSS Leading to Froxlor Application Compromise
    Critical · 9.6 CVE-2024-34070 < 2.1.9 2.1.9
  18. Froxlor username/surname AND company field Bypass
    High · 7.5 CVE-2023-50256 < 2.1.2 2.1.2
  19. Froxlor Improper Input Validation vulnerability
    Critical · 9.9 CVE-2023-6069 < 2.1.0-beta1 2.1.0-beta1
  20. Froxlor vulnerable to Improper Encoding or Escaping of Output
    Critical · 9.1 CVE-2023-3668 < 2.0.21 2.0.21
  21. Froxlor vulnerable to Path Traversal
    High · 7.2 CVE-2023-3172 < 2.0.20 2.0.20
Show more (13) Showing 21 of 34

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.

Privacy policy

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