Software weaknesses, explained simply
CWE names recurring weakness types found in software and devices; it is not a list of individual vulnerabilities. Scantide keeps the MITRE terminology visible, then explains what each weakness means and shows familiar, non-operational examples of what it can look like in a real product.
CWE-798 · Use of Hard-coded Credentials
Credentials are embedded in software, firmware, or configuration distributed with the product.
Headline signal
CWE-798 · Use of Hard-coded Credentials
Credentials are embedded in software, firmware, or configuration distributed with the product.
In plain English
Credentials are embedded in software, firmware, or configuration distributed with the product.
What this can look like
An attacker discovers a built-in administrative username and password and reuses them against other devices that shipped with the same credentials.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product contains hard-coded credentials, such as a password or cryptographic key.
Examples are intentionally conceptual. They explain the security consequence without providing exploit payloads or step-by-step attack instructions. MITRE remains the authoritative source for the CWE definition and mapping guidance.