Froxlor
39 vulnerabilities.
All published vulnerabilities with a CVE number in Froxlor products, newest first, with severity and references.
| CVE | Summary | Published | CVSS |
|---|---|---|---|
| CVE-2025-48958 | Froxlor: Froxlor is open source server administration software. Prior to version 2.2.6, an HTML Injection vulnerability in the customer account portal … | 2025-06-02 | 5.5 |
| CVE-2025-29773 | Froxlor: Froxlor is open-source server administration software. A vulnerability in versions prior to 2.2.6 allows users (such as resellers or customers) to … | 2025-03-13 | 5.8 |
| CVE-2023-50256 | Froxlor: Froxlor is open source server administration software. Prior to version 2.1.2, it was possible to submit the registration form with the essential … | 2024-01-03 | 7.5 |
| CVE-2023-6069 | Froxlor: Improper Link Resolution Before File Access in GitHub repository froxlor/froxlor prior to 2.1.0. | 2023-11-10 | 9.9 |
| CVE-2023-5564 | Froxlor: Cross-site Scripting (XSS) - Stored in GitHub repository froxlor/froxlor prior to 2.1.0-dev1. | 2023-10-12 | 4.8 |
| CVE-2023-4829 | Froxlor: Cross-site Scripting (XSS) - Stored in GitHub repository froxlor/froxlor prior to 2.0.22. | 2023-10-13 | 5.4 |
| CVE-2023-4304 | Froxlor: Business Logic Errors in GitHub repository froxlor/froxlor prior to 2.0.22,2.1.0. | 2023-08-10 | 3.8 |
| CVE-2023-3668 | Froxlor: Improper Encoding or Escaping of Output in GitHub repository froxlor/froxlor prior to 2.0.21. | 2023-07-13 | 7.2 |
| CVE-2023-3192 | Froxlor: Session Fixation in GitHub repository froxlor/froxlor prior to 2.1.0. | 2023-06-11 | 5.4 |
| CVE-2023-3173 | Froxlor: Improper Restriction of Excessive Authentication Attempts in GitHub repository froxlor/froxlor prior to 2.0.20. | 2023-06-09 | 9.8 |
| CVE-2023-3172 | Froxlor: Path Traversal in GitHub repository froxlor/froxlor prior to 2.0.20. | 2023-06-08 | 7.2 |
| CVE-2023-2666 | Froxlor: Allocation of Resources Without Limits or Throttling in GitHub repository froxlor/froxlor prior to 2.0.16. | 2023-05-11 | 7.5 |
| CVE-2023-2034 | Froxlor: Unrestricted Upload of File with Dangerous Type in GitHub repository froxlor/froxlor prior to 2.0.14. | 2023-04-13 | 8.8 |
| CVE-2023-1307 | Froxlor: Authentication Bypass by Primary Weakness in GitHub repository froxlor/froxlor prior to 2.0.13. | 2023-03-10 | 9.8 |
| CVE-2023-1033 | Froxlor: Cross-Site Request Forgery (CSRF) in GitHub repository froxlor/froxlor prior to 2.0.11. | 2023-02-25 | 8.8 |
| CVE-2023-0877 | Froxlor: Code Injection in GitHub repository froxlor/froxlor prior to 2.0.11. | 2023-02-17 | 8.8 |
| CVE-2023-0671 | Froxlor: Code Injection in GitHub repository froxlor/froxlor prior to 2.0.10. | 2023-02-04 | 8.8 |
| CVE-2023-0572 | Froxlor: Unchecked Error Condition in GitHub repository froxlor/froxlor prior to 2.0.10. | 2023-01-29 | 5.3 |
| CVE-2023-0566 | Froxlor: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in froxlor/froxlor prior to 2.0.10. | 2023-01-29 | 6.2 |
| CVE-2023-0565 | Froxlor: Business Logic Errors in GitHub repository froxlor/froxlor prior to 2.0.10. | 2023-01-29 | 5.5 |
| CVE-2023-0564 | Froxlor: Weak Password Requirements in GitHub repository froxlor/froxlor prior to 2.0.10. | 2023-01-29 | 5.4 |
| CVE-2023-0316 | Froxlor: Path Traversal: '\..\filename' in GitHub repository froxlor/froxlor prior to 2.0.0. | 2023-01-16 | 5.5 |
| CVE-2023-0315 | Froxlor: Command Injection in GitHub repository froxlor/froxlor prior to 2.0.8. | 2023-01-16 | 8.8 |
| CVE-2022-4868 | Froxlor: Improper Authorization in GitHub repository froxlor/froxlor prior to 2.0.0-beta1. | 2022-12-31 | 4.3 |
| CVE-2022-4867 | Froxlor: Cross-Site Request Forgery (CSRF) in GitHub repository froxlor/froxlor prior to 2.0.0-beta1. | 2022-12-31 | 4.3 |
| CVE-2022-4864 | Froxlor: Argument Injection in GitHub repository froxlor/froxlor prior to 2.0.0-beta1. | 2022-12-30 | 5.4 |
| CVE-2022-3869 | Froxlor: Code Injection in GitHub repository froxlor/froxlor prior to 0.10.38.2. | 2022-11-05 | 6.1 |
| CVE-2022-3721 | Froxlor: Code Injection in GitHub repository froxlor/froxlor prior to 0.10.39. | 2022-11-04 | 4.6 |
| CVE-2022-3017 | Froxlor: Cross-Site Request Forgery (CSRF) in GitHub repository froxlor/froxlor prior to 0.10.38. | 2022-08-28 | 6.5 |
| CVE-2021-42325 | Froxlor: Froxlor through 0.10.29.1 allows SQL injection in Database/Manager/DbManagerMySQL.php via a custom DB name. | 2021-10-12 | 9.8 |
| 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 … | 2022-04-13 | 6.1 |
| 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 … | 2021-10-22 | 5.4 |
| 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 … | 2020-03-09 | 5.5 |
| 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 … | 2020-03-09 | 6.1 |
| 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 … | 2020-03-09 | 8.8 |
| 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 … | 2018-06-26 | 7.2 |
| CVE-2018-12642 | Froxlor: Froxlor through 0.9.39.5 has Incorrect Access Control for tickets not owned by the current user. | 2018-06-22 | 7.5 |
| 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 … | 2017-02-13 | 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 … | 2017-09-06 | 9.8 |
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Too many to
patch at once?
Providers for vulnerability management find the affected systems in your environment, set the order and keep the patching going.