CWE · MITRE source
CWE-547Use of Hard-coded, Security-relevant Constants
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: 14 October 2026 20:41 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.
NIST 800-53 r5 controls PROPOSED for this weakness (0)AI-assisted
These are model PROPOSALS, not graded mappings. They come
from controls_to_cwe_proposals, which carries no grade field at
all; across the CWE pages 1,540 of 1,722 such associations (89%) have never
been graded by anything. The heading said “address” until
2026-09-29, which asserted a relationship the data does not carry.
Graded cross-walks are on the framework map, not here.
| 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-2025-30206 UPD | 7.5 | 9.8 | 0.0089 | 2025-04-15 |
CVE-2023-1712 UPD | 7.4 | 9.8 | 0.0085 | 2023-03-30 |
CVE-2026-28256 UPD | 7.3 | 9.8 | 0.0046 | 2026-03-12 |
CVE-2019-14837 UPD | 7.2 | 9.1 | 0.0172 | 2020-01-07 |
CVE-2024-39888 UPD | 5.7 | 7.5 | 0.0024 | 2024-07-09 |
CVE-2024-32021 UPD | 3.4 | 3.9 | 0.0102 | 2024-05-14 |
CVE-2025-23253 UPD | 2.2 | 2.5 | 0.0017 | 2025-04-22 |