EUVD-2025-209164Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
3DescriptionCVE.org
A non-default configuration in Sage DPW 2025_06_004 allows unauthenticated access to diagnostic endpoints within the Database Monitor feature, exposing sensitive information such as hashes and table names. This feature is disabled by default in all installations and never available in Sage DPW Cloud. It was forcibly disabled again in version 2025_06_003.
AnalysisAI
Unauthenticated access to diagnostic endpoints in Sage DPW 2025_06_004 Database Monitor feature discloses sensitive information including password hashes and database table names when non-default configuration is enabled. The vulnerability affects only installations with this feature explicitly enabled (disabled by default); Sage DPW Cloud is not vulnerable. This configuration was forcibly disabled in version 2025_06_003, indicating a prior history of this issue. EPSS score of 5.9 reflects moderate exploitation probability despite unauthenticated network accessibility.
Technical ContextAI
The Database Monitor feature in Sage DPW exposes diagnostic endpoints that were designed for administrative monitoring purposes. When this feature is enabled via non-default configuration, these endpoints become accessible without authentication due to insufficient access control validation. The endpoints disclose sensitive cryptographic material (password hashes) and database structural information (table names), both valuable for further attack progression. The CWE classification is not specified in available data, but the root cause involves inadequate authentication checks on diagnostic functionality. The fact that the feature is disabled by default and was forcibly disabled again in 2025_06_003 suggests this endpoint exposure represents a regression or configuration drift risk.
RemediationAI
Primary remediation is to upgrade to Sage DPW version 2025_06_003 or later, which forcibly disables this diagnostic endpoint configuration by default. For organizations requiring Database Monitor functionality, consult Sage DPW security advisories (https://www.sagedpw.at/) for any updated hardened configuration guidance or authentication controls released post-2025_06_003. Immediate mitigation for 2025_06_004 deployments is to disable the Database Monitor feature entirely through configuration management, ensuring it remains in the default disabled state. Network segmentation can provide defense-in-depth by restricting access to Sage DPW administrative interfaces to trusted internal networks only. No workarounds that maintain Database Monitor functionality while securing the endpoint are documented in available intelligence.
LibreNMS before 24.10.0 allows a remote attacker to execute arbitrary code via OS command injection involving AboutContr
Reachable assertion in Open5GS up to version 2.7.6 allows remote unauthenticated attackers to crash the Diameter CER han
A Command Injection issue in the payload build page in BYOB (Build Your Own Botnet) 2.0 allows attackers to execute arbi
Denial of service in Open5GS 2.7.6 and earlier allows network-adjacent attackers with low-privilege Diameter Gx peer acc
Denial of service in Open5GS HSS (Home Subscriber Server) versions 2.7.0 through 2.7.6 is triggered remotely by manipula
Remote command injection in Control Web Panel allows unauthenticated attackers to execute arbitrary OS commands as root
LINQPad before 5.52.01 Pro edition is vulnerable to Unsafe Deserialization in LINQPad.AutoRefManager::PopulateFromCache(
Remote code execution in dash-uploader (Python package for Plotly Dash) versions 0.1.0 through 0.7.0a2 allows unauthenti
Command injection in LiteLLM 1.18.10 lets attackers who can configure MCP (Model Context Protocol) servers supply arbitr
SQL injection in AzuraCast's backup restore flow (versions up to and including 0.23.7) lets an attacker achieve privileg
Arbitrary file read in Yu AI Code Mother v4.3 lets anonymous, remote attackers retrieve files outside the intended previ
Remote code execution in APScheduler (all versions through 3.10.x and 4.0.0a5) is achievable when applications deseriali
Same technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today