Cyber Resilience

CVE-2025-58580

Sick Enterprise Analytics

Published
06 October 2025
Modified
27 January 2026
Patch / advisory
View advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
EPSS Score 0.0034 27th percentile
Risk Priority 50 floored blend · peak EPSS

Summary

CVE-2025-58580 is a medium-severity Improper Output Neutralization for Logs (CWE-117) vulnerability in Sick Enterprise Analytics. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Indicator Removal (T1070); ranked at the 27th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A09:2025 Security Logging and Alerting Failures

EU & UK References

Vulnerability Data

An API endpoint allows arbitrary log entries to be created via POST request. Without sufficient validation of the input data, an attacker can create manipulated log entries and thus falsify or dilute logs, for example.

CWE(s)
CWE-117

Related Threats

MITRE ATT&CK Enterprise Techniques

T1070 Indicator Removal Stealth
Adversaries may selectively delete or modify artifacts generated to reduce indications of their presence and blend in with legitimate activity.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-58578Same product: Sick Enterprise Analytics
CVE-2025-58583Same product: Sick Enterprise Analytics
CVE-2025-58581Same product: Sick Enterprise Analytics
CVE-2025-58582Same product: Sick Enterprise Analytics
CVE-2024-52962Shared CWE-117
CVE-2024-7696Shared CWE-117
CVE-2025-0754Shared CWE-117
CVE-2025-36625Shared CWE-117
CVE-2025-54656Shared CWE-117
CVE-2025-25294Shared CWE-117

Affected Assets

sick
enterprise analytics
all versions

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover missing or incorrect output neutralization when log messages are constructed from untrusted input.

SI-10 Information Input Validation partial match

Input validation reduces the chance that specially crafted data reaches log-message construction routines.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices and coding standards directly require output sanitization for logs.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect log injection flaws but does not prevent them at the source.

A.8.15 Logging partial match
degrades

Logging control directly requires proper log generation and handling, which mitigates improper output neutralization.

A.8.16 Monitoring activities partial match
finds

Monitoring activities rely on trustworthy logs but do not ensure log message integrity.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC includes coding standards that reduce log-related weaknesses but does not specifically address logging.

A.8.28 Secure coding partial match
prevents

Secure coding practices mandate input validation and output encoding, directly preventing log injection.

References