SICK Enterprise Analytics CVE-2025-58581

Exploitation requires an authenticated session to SICK Enterprise Analytics (PR:L) and the ability to induce an application error that returns the verbose stack trace - the condition is that the application returns full stack traces to users on error rather than a generic error page. No user interaction by a victim and no non-default toggle is described; the behavior appears inherent to error handling. Limiting factors: the attacker must already hold valid low-level credentials, and the payoff is limited to confidentiality of internal application metadata (C:L) - no integrity or availability impact and no direct data exfiltration beyond diagnostic information.

This is a low-to-moderate priority information disclosure issue, not an urgent threat. The provided CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, base 4.3) is internally consistent with CWE-200 and the description: network-reachable, low complexity, but requiring low-level privileges (PR:L, an authenticated user) and yielding only limited confidentiality impact (C:L) with no integrity or availability effect. The EPSS score of 0.33% (24th percentile) reinforces low near-term exploitation likelihood, and the CVE is NOT on CISA KEV, so there is no public exploit identified at time of analysis. All signals are concordant - a genuinely low-risk, low-severity flaw rather than a high-CVSS-but-overstated issue. The practical value is as a reconnaissance aid: leaked class/method names and stack internals help an attacker fingerprint technology and application structure to chain against more serious flaws, but the issue itself grants no code execution or data modification. No SSVC decision data was supplied in the input, so exploitation-automatable/technical-impact framing cannot be evaluated here.

An authenticated user of SICK Enterprise Analytics deliberately triggers an application error (e.g., via malformed input or an unexpected request) and receives a full stack trace in the response. They harvest the disclosed class names, method names, and internal paths to map the application's frameworks and structure, using that reconnaissance to plan follow-on attacks. No public exploit code is known; exploitation requires only normal product access and no special tooling.