Fossbilling
12 vulnerabilities.
All published vulnerabilities with a CVE number in Fossbilling products, newest first, with severity and references.
| CVE | Summary | Published | CVSS |
|---|---|---|---|
| CVE-2023-4005 | Fossbilling: Insufficient Session Expiration in GitHub repository fossbilling/fossbilling prior to 0.5.5. | 2023-07-30 | 9.8 |
| CVE-2023-3568 | Fossbilling: Open Redirect in GitHub repository alextselegidis/easyappointments prior to 1.5.0. | 2023-07-10 | 6.3 |
| CVE-2023-3521 | Fossbilling: Cross-site Scripting (XSS) - Reflected in GitHub repository fossbilling/fossbilling prior to 0.5.4. | 2023-07-06 | 6.1 |
| CVE-2023-3493 | Fossbilling: Improper Neutralization of Formula Elements in a CSV File in GitHub repository fossbilling/fossbilling prior to 0.5.3. | 2023-06-30 | 8.0 |
| CVE-2023-3491 | Fossbilling: Unrestricted Upload of File with Dangerous Type in GitHub repository fossbilling/fossbilling prior to 0.5.3. | 2023-06-30 | 8.8 |
| CVE-2023-3490 | Fossbilling: SQL Injection in GitHub repository fossbilling/fossbilling prior to 0.5.3. | 2023-06-30 | 9.8 |
| CVE-2023-3394 | Fossbilling: Session Fixation in GitHub repository fossbilling/fossbilling prior to 0.5.1. | 2023-06-23 | 5.4 |
| CVE-2023-3393 | Fossbilling: Code Injection in GitHub repository fossbilling/fossbilling prior to 0.5.1. | 2023-06-23 | 7.2 |
| CVE-2023-3230 | Fossbilling: Missing Authorization in GitHub repository fossbilling/fossbilling prior to 0.5.0. | 2023-06-14 | 7.5 |
| CVE-2023-3229 | Fossbilling: Business Logic Errors in GitHub repository fossbilling/fossbilling prior to 0.5.0. | 2023-06-14 | 6.5 |
| CVE-2023-3228 | Fossbilling: Business Logic Errors in GitHub repository fossbilling/fossbilling prior to 0.5.0. | 2023-06-14 | 5.7 |
| CVE-2023-3227 | Fossbilling: Insufficient Granularity of Access Control in GitHub repository fossbilling/fossbilling prior to 0.5.0. | 2023-06-14 | 5.7 |
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.