CWE-547: Use of Hard-coded, Security-relevant Constants
10 CVEs have CWE-547 as their primary weakness. 0 of them are in the CISA KEV catalog. The highest EPSS score among them is 1.718%.
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.
Child of CWE-1078: Inappropriate Source Code Style or Formatting
OWASP Top 10: A05:2021 Security Misconfiguration · A02:2025 Security Misconfiguration
Mitigations
- Implementation: Avoid using hard-coded constants. Configuration files offer a more flexible solution.
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cwe_lookup/CWE-547'curl 'https://api.contrastcyber.com/cve_search?cwe_id=CWE-547'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- OWASP Top 10 categories by the OWASP Foundation (CC BY 3.0).
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).