CVE-2025-59093
Raw vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2025-59093 is a high-severity Reliance on Security Through Obscurity (CWE-656) vulnerability in Sec Consult (inferred from references). Its CVSS base score is 8.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique System Information Discovery (T1082); ranked at the 9th 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-8 (Security and Privacy Engineering Principles) and SC-13 (Cryptographic Protection) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-206354
Vulnerability Data
Exos 9300 instances are using a randomly generated database password to connect to the configured MSSQL server. The password is derived from static random values, which are concatenated to the hostname and a random string that can be read by…
more
every user from the registry. This allows an attacker to derive the database password and get authenticated access to the central exos 9300 database as the user Exos9300Common. The user has the roles ExosDialog and ExosDialogDotNet assigned, which are able to read most tables of the database as well as update and insert into many tables.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.3.4
Mitigating Controls (NIST 800-53 r5) AI
Requires selection and implementation of approved cryptographic methods whose strength does not rest on secrecy of design.
Security and privacy engineering principles explicitly prohibit reliance on obscurity and require documented, verifiable protection mechanisms.
Requires cryptographic or equivalent protection of information at rest, eliminating dependence on obscurity for confidentiality.
Mandates actual cryptographic or equivalent protection of transmitted data rather than depending on hidden algorithms or keys.
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.
Secure SDLC practices explicitly reject obscurity-based designs in favor of proven controls.
Risk-management policy can mandate avoidance of obscurity but does not itself implement technical alternatives.
Risk analysis surfaces obscurity as a weakness yet does not prevent its introduction.
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.
Mandates use of cryptography whose strength is independent of secrecy of design or keys.
Requires secure architecture and engineering principles that reject reliance on obscurity.
Requires authentication mechanisms whose strength does not depend on secrecy of implementation.
Secure-coding rules prohibit hidden or undocumented security mechanisms.
Security testing can expose mechanisms whose only protection is obscurity.