SICK AG Baggage Analytics vulnerabilities
13 vulnerabilities
Known vulnerabilities in SICK AG Baggage Analytics, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.
CVE-2025-9913sick agbaggage analytics+3
EPSS score0.29%
JavaScript can be ran inside the address bar via the dashboard "Open in new Tab" Button, making the application vulnerable to session hijacking.CVE-2025-9914sick agbaggage analytics+3EPSS score0.32%
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.CVE-2025-58589sick agbaggage analytics+3EPSS score0.36%
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.CVE-2025-58585sick agbaggage analytics+3EPSS score0.43%
Multiple endpoints with sensitive information do not require authentication, making the application susceptible to information gathering.CVE-2025-58591sick agbaggage analytics+3EPSS score0.53%
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.CVE-2025-58587sick agbaggage analytics+4EPSS score0.49%
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.CVE-2025-58586sick agbaggage analytics+4EPSS score0.36%
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.CVE-2025-58584sick agbaggage analytics+4EPSS score0.39%
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.CVE-2025-58590sick agbaggage analytics+7EPSS score0.53%
It's possible to brute force folders and files, what can be used by an attacker to steal sensitve information.CVE-2025-58579sick agbaggage analytics+4EPSS score0.40%
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.CVE-2025-49186avayamedia_server+5EPSS score0.37%
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.CVE-2025-49184sick agbaggage analytics+5EPSS score0.49%
A remote unauthorized attacker may gather sensitive information of the application, due to missing authorization of configuration settings of the product.CVE-2025-49193sick agbaggage analytics+6EPSS score0.31%
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).