CVE-2025-58584: Plain Text Transmission of Username and Password in the URL
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.
Security readout for executives and security teams
Plain-English summary
This flaw can expose usernames and passwords because affected SICK analytics products transmit them in URLs. URLs often end up in logs, browser history, proxies, or monitoring systems, so credential leakage may occur without a direct breach of the application itself.
Executive priority
Treat this as a moderate credential-exposure issue. Prioritize environments where affected SICK systems are exposed beyond trusted operational networks or where URL logging is broad and long retained.
Technical view
CVE-2025-58584 is CWE-598: credentials are passed as URL parameters in HTTP requests. The CVSS 3.1 score is 5.3, reflecting network reachability and low attack complexity, but limited confidentiality impact only. The source bundle does not identify integrity or availability impact.
Likely exposure
Exposure is limited to organizations using the listed SICK AG analytics products: Baggage Analytics, Tire Analytics, Package Analytics, Logistic Diagnostic Analytics, and Enterprise Analytics. Risk is higher where requests pass through proxies, shared browsers, server logs, or centralized monitoring.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. Practical risk comes from unintended credential disclosure through stored URLs rather than a complex exploit chain. Evidence of public exploitation is incomplete in the source bundle.
Researcher notes
The bundle identifies the weakness and affected product families but does not include detailed fixed versions, exploit observations, or compensating controls beyond vendor and ICS guidance references. Avoid assuming patch availability without checking SICK’s advisory.
Mitigation direction
Check SICK PSIRT and advisory SCA-2025-0010 for vendor-provided fixes or configuration guidance.
Rotate credentials that may have appeared in affected product URLs or logs.
Restrict access to affected analytics interfaces using ICS network segmentation practices.
Limit retention and access for web, proxy, browser, WAF, and SIEM URL logs.
Follow SICK cybersecurity operating guidelines for hardening and operational controls.
Validation and detection
Inventory deployments of the affected SICK analytics products and versions.
Review authentication flows for usernames or passwords appearing in URL parameters.
Check web, proxy, WAF, and SIEM logs for historical credential exposure.
Confirm whether affected systems are reachable from untrusted networks.
Track SICK advisory SCA-2025-0010 for product-specific remediation status.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-598: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4SICK AG
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-598 · source CWE mapping
Use of HTTP Request With Sensitive Query String
Use of HTTP Request With Sensitive Query String represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.