This page lists publicly disclosed CVE vulnerabilities affecting sick tire_analytics (linked via NVD CPE). Each row includes severity scores, summaries, and publication dates to help identify and analyze security issues.
| CVE | Summary | Source | Max CVSS | EPSS % | Published | Updated |
|---|---|---|---|---|---|---|
| CVE-2025-9914 | The credentials of the users stored in the system's local database can be used for the log in, making it possible for an attacker to gain unauthorized access. This could potentially affect the confidentiality of the application. | [email protected] | 4.3 | 0.06% | 2025-10-06 | 2026-01-29 |
| CVE-2025-9913 | JavaScript can be ran inside the address bar via the dashboard "Open in new Tab" Button, making the application vulnerable to session hijacking. | [email protected] | 4.5 | 0.05% | 2025-10-06 | 2026-01-29 |
| CVE-2025-58591 | A remote, unauthorized attacker can brute force folders and files and read them like private keys or configurations, making the application vulnerable for gathering sensitive information. | [email protected] | 6.5 | 0.06% | 2025-10-06 | 2026-01-27 |
| CVE-2025-58590 | It's possible to brute force folders and files, what can be used by an attacker to steal sensitve information. | [email protected] | 6.5 | 0.06% | 2025-10-06 | 2026-01-27 |
| CVE-2025-58589 | When an error occurs in the application a full stacktrace is provided to the user. The stacktrace lists class and method names as well as other internal information. An attacker thus receives information about the technology used and the structure of the application. | [email protected] | 2.7 | 0.05% | 2025-10-06 | 2026-01-27 |
| CVE-2025-58587 | The application does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame, making it possible for an attacker to guess user credentials. | [email protected] | 6.5 | 0.19% | 2025-10-06 | 2026-01-27 |
| CVE-2025-58586 | For failed login attempts, the application returns different error messages depending on whether the login failed due to an incorrect password or a non-existing username. This allows an attacker to guess usernames until they find an existing one. | [email protected] | 5.3 | 0.06% | 2025-10-06 | 2026-01-27 |
| CVE-2025-58585 | Multiple endpoints with sensitive information do not require authentication, making the application susceptible to information gathering. | [email protected] | 5.3 | 0.06% | 2025-10-06 | 2026-01-27 |
| CVE-2025-58584 | In the HTTP request, the username and password are transferred directly in the URL as parameters. However, URLs can be stored in various systems such as server logs, browser histories or proxy servers. As a result, there is a high risk that this sensitive data will be disclosed unintentionally. | [email protected] | 5.3 | 0.05% | 2025-10-06 | 2026-01-27 |
| CVE-2025-58579 | Due to a lack of authentication, it is possible for an unauthenticated user to request data from this endpoint, making the application vulnerable for user enumeration. | [email protected] | 5.3 | 0.08% | 2025-10-06 | 2026-01-27 |
| CVE-2025-49193 | The application fails to implement several security headers. These headers help increase the overall security level of the web application by e.g., preventing the application to be displayed in an iFrame (Clickjacking attacks) or not executing injected malicious JavaScript code (XSS attacks). | [email protected] | 4.2 | 0.29% | 2025-06-12 | 2026-01-26 |
| CVE-2025-49186 | The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame, making it susceptible to brute-force attacks. | [email protected] | 5.3 | 0.29% | 2025-06-12 | 2026-02-03 |
| CVE-2025-49184 | A remote unauthorized attacker may gather sensitive information of the application, due to missing authorization of configuration settings of the product. | [email protected] | 7.5 | 0.39% | 2025-06-12 | 2026-01-29 |