Cyber Resilience

CWE · MITRE source

CWE-547Use of Hard-coded, Security-relevant Constants

Abstraction: Base · CVEs in our corpus: 11

The product uses hard-coded constants instead of symbolic names for security-critical values, which increases the likelihood of mistakes during code maintenance or security policy change.

If the developer does not find all occurrences of the hard-coded constants, an incorrect policy decision may be made if one of the constants is not changed. Making changes to these values will require code changes that may be difficult or impossible once the system is released to the field. In addition, these hard-coded values may become available to attackers if the code is ever disclosed.

Last updated: 20 August 2026 13:14 UTC

OWASP Top 10 for Web (2025)

This weakness contributes to A02:2025 Security Misconfiguration.

Control responseHuman-reviewed

Answering this weakness across the control lifecycle, from our framework cross-walks.

Prevent
Stop it (NIST 800-53 / CSF Protect)
  • PR.PS-06
  • CM-6 Configuration Settings
  • SA-15 Development Process, Standards, and Tools
Detect
Catch it (CSF Detect / Respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)

NIST 800-53 r5 controls that address this weakness (0)AI-assisted

Control Title Family Why it addresses this CWE
No NIST controls proposed yet.

Top CVEs of this weakness type, ranked by Risk Priority

CVE Risk CVSS EPSS Published
CVE-2023-1712 7.49.80.00852023-03-30
CVE-2025-30206 7.49.80.00802025-04-15
CVE-2019-14837 7.29.10.01722020-01-07
CVE-2026-28256 7.29.80.00272026-03-12
CVE-2024-39888 5.77.50.00242024-07-09
CVE-2024-32021 3.43.90.01022024-05-14
CVE-2025-23253 2.22.50.00162025-04-22