CVE-2023-40726
Siemens Qms Automotive ≤ 12.39
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-40726 is a high-severity Server-generated Error Message Containing Sensitive Information (CWE-550) vulnerability in Siemens Qms Automotive. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Protocol or Service Impersonation (T1001.003); ranked in the top 48% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-45280
Vulnerability Data
A vulnerability has been identified in QMS Automotive (All versions < V12.39). The affected application server responds with sensitive information about the server. This could allow an attacker to directly access the database.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V14.2.1
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.
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.
Logging policy can require suppression of sensitive data in error responses.
Secure SDLC mandates handling of error messages to avoid information disclosure.
A.8.26 only requires that error message handling be identified as a possible security requirement during requirements gathering; it does not mandate, enforce or implement any restriction on sensitive information in those messages, so the weakness can still be present and exploitable.
A.8.27 mandates establishing and applying secure engineering principles (defense-in-depth, least privilege, security by design, hardening, zero-trust) and performing security-oriented design reviews; it does not stop server error messages from containing sensitive information when the error condition occurs.
Secure coding standards prohibit embedding sensitive data in server error messages.
Security testing can detect and require remediation of verbose error messages.