Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2024-5514 is a critical-severity Use of Hard-coded Credentials (CWE-798) vulnerability in Org (inferred from references). Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Unsecured Credentials (T1552); ranked at the 48th 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 CM-2 (Baseline Configuration) and CM-7 (Least Functionality) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-47119
Vulnerability Data
MinMax CMS from MinMax Digital Technology contains a hidden administrator account with a fixed password that cannot be removed or disabled from the management interface. Remote attackers who obtain this account can bypass IP access control restrictions and log in…
more
to the backend system without being recorded in the system logs.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Maintaining and reviewing a documented baseline configuration allows comparison that reveals any functionality absent from the approved specification.
Least-functionality configuration explicitly prohibits or restricts any capability not required by the approved baseline, blocking hidden additions.
Authenticator management requires secure distribution and handling of credentials, structurally discouraging hard-coded values.
Developer testing and evaluation activities are designed to discover undocumented or unspecified functionality after it has been introduced.
Cryptographic key management mandates proper establishment and handling instead of embedding keys in code.
Documented development processes and standards require all functionality to be specified and visible, structurally preventing undocumented hidden features.
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 directly prevent introduction of undocumented hidden functionality during development.
Pre-acquisition integrity/authenticity checks can detect undocumented hidden functions in supplied software/hardware.
PR.AA-01's credential/key-management processes can reduce the incentive to embed secrets but do not address or detect hard-coded values in source code, so the weakness remains fully possible.
PR.AA-02 addresses human identity proofing and per-person credential issuance at enrollment; it has no bearing on whether developers embed static credentials in software.
PR.DS-01 addresses encryption and integrity of stored data but never touches credential or key management practices, so it neither prevents hard-coded credentials nor removes any of their risk.
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.
Security testing in development and acceptance can discover undocumented functionality before release.
Change management processes can catch unauthorized additions but do not inherently prevent hidden functionality from being introduced.
Education on secure configuration practices discourages technical staff from embedding or relying on hard-coded credentials in systems and applications.
Monitoring activities can detect anomalous behavior from hidden functions but do not eliminate the weakness.
Secure key-generation, distribution and storage procedures reduce the likelihood that hard-coded or default cryptographic keys will be introduced or left unprotected.
Secure development life cycle mandates documented requirements and design reviews that would expose undocumented hidden functionality.