Vulnerability database · updated every 15 minutes
New vulnerabilities in the software websites run.
CVEs and security advisories for WordPress, its plugins and themes, npm, PyPI and the servers behind websites, merged from NVD, the CVE Program, GitHub, OSV.dev and WPVulnerability, with CISA's list of the ones attackers exploit.
- Tracked
- 54,972
- Published in 7 days
- 1,564
- Critical in 30 days
- 518
- Actively exploited
- 541
Results for “Froxlor”
97 vulnerabilities- High 7.5
CVE-2026-41231 · Froxlor
Incomplete Symlink Validation in DataDump.add() Allows Arbitrary Directory Ownership Takeover via Cron
Published 15 Apr 2026 · Fixed in 2.3.6 · NVD, Project advisories (GitHub) - High 8.5
CVE-2026-41230 · Froxlor
BIND Zone File Injection via Unsanitized DNS Record Content in DomainZones::add()
Published 15 Apr 2026 · Fixed in 2.3.6 · NVD, Project advisories (GitHub) - Critical 9.1
CVE-2026-41229 · Froxlor
PHP Code Injection via Unescaped Single Quotes in userdata.inc.php Generation (MysqlServer API)
Published 15 Apr 2026 · Fixed in 2.3.6 · NVD, Project advisories (GitHub) - Critical 9.9
CVE-2026-41228 · Froxlor
Local File Inclusion via path traversal in API `def_language` parameter leads to Remote Code Execution
Published 15 Apr 2026 · Fixed in 2.3.6 · NVD, Project advisories (GitHub) - High 8.6
CVE-2026-30932 · Froxlor
BIND zone file injection via unsanitized DNS record content in DomainZones API
Published 24 Mar 2026 · Fixed in 2.3.5 · NVD, Project advisories (GitHub) - Critical 9.1
CVE-2026-26279 · Froxlor
Admin-to-Root Privilege Escalation via Input Validation Bypass + OS Command Injection
Published 3 Mar 2026 · Fixed in 2.3.4 · NVD, Project advisories (GitHub) - Medium 5.4
CVE-2025-48958 · Froxlor
HTML Injection
Published 11 Mar 2025 · Fixed in 2.2.6 · NVD, Project advisories (GitHub) - High 7.8
CVE-2025-29773 · Froxlor
Multiple Accounts Can Share the Same Email Address Leading to Potential Privilege Escalation or Account Takeover
Published 11 Mar 2025 · NVD, Project advisories (GitHub) - High 7.3
GHSA-34qg-65m4-f23m · Froxlor
/etc/pure-ftpd/db/mysql.conf is chmod 644 but contains <SQL_UNPRIVILEGED_PASSWORD>
Published 23 Aug 2024 · Fixed in 2.2.0 · Project advisories (GitHub) - Critical 9.6
CVE-2024-34070 · Froxlor
Blind XSS Leading to Froxlor Application Compromise
Published 10 May 2024 · Fixed in 2.1.9 · Project advisories (GitHub) - High 7.5
CVE-2023-50256 · Froxlor
Froxlor username/surname AND company field Bypass
Published 3 Jan 2024 · Fixed in 2.1.2 · NVD, Project advisories (GitHub) - High 8.8
CVE-2023-6069 · Froxlor
Improper Link Resolution Before File Access in GitHub repository froxlor/froxlor prior to 2.1.0.
Published 10 Nov 2023 · Fixed in 2.1.0 · NVD - Medium 5.4
CVE-2023-4829 · Froxlor
Cross-site Scripting (XSS) - Stored in GitHub repository froxlor/froxlor prior to 2.0.22.
Published 13 Oct 2023 · Fixed in 2.0.22 · NVD - Medium 4.8
CVE-2023-5564 · Froxlor
Cross-site Scripting (XSS) - Stored in GitHub repository froxlor/froxlor prior to 2.1.0-dev1.
Published 13 Oct 2023 · Fixed in 2.1.0 · NVD - Low 2.7
CVE-2023-4304 · Froxlor
Business Logic Errors in GitHub repository froxlor/froxlor prior to 2.0.22,2.1.0.
Published 11 Aug 2023 · Fixed in 2.0.22 · NVD - High 7.2
CVE-2023-3668 · Froxlor
Improper Encoding or Escaping of Output in GitHub repository froxlor/froxlor prior to 2.0.21.
Published 14 Jul 2023 · Fixed in 2.0.21 · NVD - Medium 5.4
CVE-2023-3192 · Froxlor
Session Fixation in GitHub repository froxlor/froxlor prior to 2.1.0.
Published 11 Jun 2023 · Fixed in 2.1.0 · NVD - Critical 9.8
CVE-2023-3173 · Froxlor
Improper Restriction of Excessive Authentication Attempts in GitHub repository froxlor/froxlor prior to 2.0.20.
Published 9 Jun 2023 · Fixed in 2.0.20 · NVD - High 7.2
CVE-2023-3172 · Froxlor
Path Traversal in GitHub repository froxlor/froxlor prior to 2.0.20.
Published 9 Jun 2023 · Fixed in 2.0.20 · NVD - High 7.5
CVE-2023-2666 · Froxlor
Allocation of Resources Without Limits or Throttling in GitHub repository froxlor/froxlor prior to 2.0.16.
Published 12 May 2023 · Fixed in 2.0.16 · NVD - High 8.8
CVE-2023-2034 · Froxlor
Unrestricted Upload of File with Dangerous Type in GitHub repository froxlor/froxlor prior to 2.0.14.
Published 14 Apr 2023 · Fixed in 2.0.14 · NVD - Critical 9.8
CVE-2023-1307 · Froxlor
Authentication Bypass by Primary Weakness in GitHub repository froxlor/froxlor prior to 2.0.13.
Published 10 Mar 2023 · Fixed in 2.0.13 · NVD - High 8.8
CVE-2023-1033 · Froxlor
Cross-Site Request Forgery (CSRF) in GitHub repository froxlor/froxlor prior to 2.0.11.
Published 25 Feb 2023 · Fixed in 2.0.11 · NVD - High 8.8
CVE-2023-0877 · Froxlor
Code Injection in GitHub repository froxlor/froxlor prior to 2.0.11.
Published 17 Feb 2023 · Fixed in 2.0.11 · NVD - High 8.8
CVE-2023-0671 · Froxlor
Code Injection in GitHub repository froxlor/froxlor prior to 2.0.10.
Published 4 Feb 2023 · Fixed in 2.0.10 · NVD - Medium 5.3
CVE-2023-0572 · Froxlor
Unchecked Error Condition in GitHub repository froxlor/froxlor prior to 2.0.10.
Published 29 Jan 2023 · Fixed in 2.0.10 · NVD - Medium 4.8
CVE-2023-0566 · Froxlor
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in froxlor/froxlor prior to 2.0.10.
Published 29 Jan 2023 · Fixed in 2.0.10 · NVD - Medium 4.9
CVE-2023-0565 · Froxlor
Business Logic Errors in GitHub repository froxlor/froxlor prior to 2.0.10.
Published 29 Jan 2023 · Fixed in 2.0.10 · NVD - High 7.5
CVE-2023-0564 · Froxlor
Weak Password Requirements in GitHub repository froxlor/froxlor prior to 2.0.10.
Published 29 Jan 2023 · Fixed in 2.0.10 · NVD - Medium 5.5
CVE-2023-0316 · Froxlor
Path Traversal: '\..\filename' in GitHub repository froxlor/froxlor prior to 2.0.0.
Published 16 Jan 2023 · Fixed in 2.0.0 · NVD - High 8.8
CVE-2023-0315 · Froxlor
Command Injection in GitHub repository froxlor/froxlor prior to 2.0.8.
Published 16 Jan 2023 · Fixed in 2.0.8 · NVD - Medium 4.3
CVE-2022-4868 · Froxlor
Improper Authorization in GitHub repository froxlor/froxlor prior to 2.0.0-beta1.
Published 31 Dec 2022 · NVD - Medium 4.3
CVE-2022-4867 · Froxlor
Cross-Site Request Forgery (CSRF) in GitHub repository froxlor/froxlor prior to 2.0.0-beta1.
Published 31 Dec 2022 · NVD - Medium 5.4
CVE-2022-4864 · Froxlor
Argument Injection in GitHub repository froxlor/froxlor prior to 2.0.0-beta1.
Published 30 Dec 2022 · NVD - Medium 6.1
CVE-2022-3869 · Froxlor
Code Injection in GitHub repository froxlor/froxlor prior to 0.10.38.2.
Published 5 Nov 2022 · Fixed in 0.10.38.2 · NVD - Medium 4.6
CVE-2022-3721 · Froxlor
Code Injection in GitHub repository froxlor/froxlor prior to 0.10.39.
Published 4 Nov 2022 · Fixed in 0.10.39 · NVD - Medium 6.5
CVE-2022-3017 · Froxlor
Cross-Site Request Forgery (CSRF) in GitHub repository froxlor/froxlor prior to 0.10.38.
Published 28 Aug 2022 · Fixed in 0.10.38 · NVD - Medium 6.1
CVE-2020-29653 · Froxlor
Froxlor through 0.10.22 does not perform validation on user input passed in the customermail GET parameter. The value of this parameter is reflected in the login webpage, allowing the injection of arbitrary HTML tags.
Published 13 Apr 2022 · NVD - Medium 5.4
CVE-2020-28957 · Froxlor
Multiple cross-site scripting (XSS) vulnerabilities in the Customer Add module of Foxlor v0.10.16 allows attackers to execute arbitrary web scripts or HTML via a crafted payload entered into the name, firstname, or username input fields.
Published 22 Oct 2021 · NVD - Critical 9.8
CVE-2021-42325 · Froxlor
Froxlor through 0.10.29.1 allows SQL injection in Database/Manager/DbManagerMySQL.php via a custom DB name.
Published 12 Oct 2021 · Fixed in 0.10.30 · NVD - Medium 5.5
CVE-2020-10237 · Froxlor
An issue was discovered in Froxlor through 0.10.15. The installer wrote configuration parameters including passwords into files in /tmp, setting proper permissions only after writing the sensitive data. A local attacker could have disclosed the information if he read the file at the right time, because of _createUserdataConf in install/lib/class.FroxlorInstall.php.
Published 9 Mar 2020 · NVD - Medium 6.1
CVE-2020-10236 · Froxlor
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.
Published 9 Mar 2020 · Fixed in 0.10.14 · NVD - High 8.8
CVE-2020-10235 · Froxlor
An issue was discovered in Froxlor before 0.10.14. Remote attackers with access to the installation routine could have executed arbitrary code via the database configuration options that were passed unescaped to exec, because of _backupExistingDatabase in install/lib/class.FroxlorInstall.php.
Published 9 Mar 2020 · Fixed in 0.10.14 · NVD - High 7.2
CVE-2018-1000527 · Froxlor
Froxlor version <= 0.9.39.5 contains a PHP Object Injection vulnerability in Domain name form that can result in Possible information disclosure and remote code execution. This attack appear to be exploitable via Passing malicious PHP objection in $_POST['ssl_ipandport']. This vulnerability appears to have been fixed in after commit c1e62e6.
Published 26 Jun 2018 · NVD - High 7.5
CVE-2018-12642 · Froxlor
Froxlor through 0.9.39.5 has Incorrect Access Control for tickets not owned by the current user.
Published 22 Jun 2018 · NVD - Critical 9.8
CVE-2015-5959 · Froxlor
Froxlor before 0.9.33.2 with the default configuration/setup might allow remote attackers to obtain the database password by reading /logs/sql-error.log.
Published 6 Sept 2017 · NVD - Critical 9.8
CVE-2016-5100 · Froxlor
Froxlor before 0.9.35 uses the PHP rand function for random number generation, which makes it easier for remote attackers to guess the password reset token by predicting a value.
Published 13 Feb 2017 · NVD
Where it comes from
The list holds every advisory UpHeron reads for the software it watches: WordPress and every plugin and theme its plugin reports, the packages in monitored repositories and manifests, and the servers and frameworks found on monitored websites. One vulnerability from several sources is one entry, under its CVE.
- NVD, the US National Vulnerability Database. This product uses the NVD API but is not endorsed or certified by the NVD.
- New and changed records of the CVE Program, read every 15 minutes, so a rating or fix added after a CVE is published reaches the list, and its alerts, within the hour. CVE content © 1999–2026 The MITRE Corporation, used under the CVE terms of use; CVE® is a registered trademark of The MITRE Corporation.
- OSV.dev, with the GitHub Advisory Database (CC BY 4.0).
- WPVulnerability (CC0) for WordPress plugins and themes, and WordPress's own security advisories.
- Node.js's own security release posts, read every 15 minutes, which name its vulnerabilities the day they are fixed, days before their CVE records.
- The security advisories projects publish on GitHub, and the CVEs libraries such as Brotli name in their release notes, which also count for the runtimes that bundle them.
- CISA's Known Exploited Vulnerabilities catalog.
Each day's new ones, grouped, and every critical one as soon as we find it: on the blog.
Run WordPress? The UpHeron plugin alerts you the day one of these affects your own site.