Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

CWE-798 (使用硬编码的凭证) — Vulnerability Class 684

684 vulnerabilities classified as CWE-798 (使用硬编码的凭证). AI Chinese analysis included.

CWE-798 represents a critical security weakness where authentication mechanisms rely on static, embedded credentials rather than dynamic verification. This flaw typically manifests as default administrative accounts with simple, hard-coded passwords or cryptographic keys stored directly within the source code or configuration files. Attackers exploit this vulnerability by scanning for these predictable credentials, gaining immediate, unauthorized access to sensitive systems without needing to bypass complex security controls. To mitigate this risk, developers must eliminate static secrets entirely, implementing robust credential management solutions such as secure vaults, environment variables, or hardware security modules. Additionally, enforcing strong password policies, regular key rotation, and multi-factor authentication ensures that access rights are dynamic and secure, significantly reducing the attack surface against unauthorized entry.

MITRE CWE Description
The product contains hard-coded credentials, such as a password or cryptographic key. There are two main variations: Inbound: the product contains an authentication mechanism that checks the input credentials against a hard-coded set of credentials. In this variant, a default administration account is created, and a simple password is hard-coded into the product and associated with that account. This hard-coded password is the same for each installation of the product, and it usually cannot be changed or disabled by system administrators without manually modifying the program, or otherwise patching the product. It can also be difficult for the administrator to detect. Outbound: the product connects to another system or component, and it contains hard-coded credentials for connecting to that component. This variant applies to front-end systems that authenticate with a back-end service. The back-end service may require a fixed password that can be easily discovered. The programmer may simply hard-code those back-end credentials into the front-end product.
Common Consequences (2)
Access Control Bypass Protection Mechanism
If hard-coded passwords are used, it is almost certain that malicious users will gain access to the account in question. Any user of the product that hard-codes passwords may be able to extract the password. Client-side systems with hard-coded passwords pose even more of a threat, since the extracti…
Integrity, Confidentiality, Availability, Access Control, Other Read Application Data, Gain Privileges or Assume Identity, Execute Unauthorized Code or Commands, Other
This weakness can lead to the exposure of resources or functionality to unintended actors, possibly providing attackers with sensitive information or even execute arbitrary code. If the password is ever discovered or published (a common occurrence on the Internet), then anybody with knowledge of thi…
Mitigations (5)
Architecture and Design For outbound authentication: store passwords, keys, and other credentials outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320). If you cannot use encryption to protect the file, then make sure that the permissions are as restrictive as …
Architecture and Design For inbound authentication: Rather than hard-code a default username and password, key, or other authentication credentials for first time logins, utilize a "first login" mode that requires the user to enter a unique strong password or key.
Architecture and Design If the product must contain hard-coded credentials or they cannot be removed, perform access control checks and limit which entities can access the feature that requires the hard-coded credentials. For example, a feature might only be enabled through the system console instead of through a network connection.
Architecture and Design For inbound authentication using passwords: apply strong one-way hashes to passwords and store those hashes in a configuration file or database with appropriate access control. That way, theft of the file/database still requires the attacker to try to crack the password. When handling an incoming password during authentication, take the hash of the password and compare it to the saved hash. Use ra…
Architecture and Design For front-end to back-end connections: Three solutions are possible, although none are complete. The first suggestion involves the use of generated passwords or keys that are changed automatically and must be entered at given time intervals by a system administrator. These passwords will be held in memory and only be valid for the time intervals. Next, the passwords or keys should be limited at th…
Examples (2)
The following code uses a hard-coded password to connect to a database:
... DriverManager.getConnection(url, "scott", "tiger"); ...
Bad · Java
javap -c ConnMngr.class 22: ldc #36; //String jdbc:mysql://ixne.com/rxsql 24: ldc #38; //String scott 26: ldc #17; //String tiger
Attack
The following code is an example of an internal hard-coded password in the back-end:
int VerifyAdmin(char *password) { if (strcmp(password, "Mew!")) { printf("Incorrect Password!\n"); return(0) } printf("Entering Diagnostic Mode...\n"); return(1); }
Bad · C
int VerifyAdmin(String password) { if (!password.equals("Mew!")) { return(0) } //Diagnostic Mode return(1); }
Bad · Java
CVE ID Title CVSS Severity Published
CVE-2026-84034 IBM Guardium Data Protection is affected by multiple vulnerabilities. — Guardium Data Protection 8.8 High 2026-09-18
CVE-2026-77960 Use of Hard-coded Credentials in Bransys ELD — ELD 5.3 Medium 2026-09-18
CVE-2026-86520 Use of Hard-coded Credentials in Bransys ELD — ELD 7.5 High 2026-09-18
CVE-2026-81440 Dell OpenManage Server Administrator 11.1.0.3前硬编码凭据漏洞 — OpenManage Server Administrator Managed Node (Patch) for Windows 7.3 High 2026-09-17
CVE-2026-92787 Feast through 0.66.0 Authentication Bypass via Unverified Token — feast 9.8 Critical 2026-09-16
CVE-2026-68950 Use of Hard-coded Credentials in Digital Watchdog VMAX DVR and NVR Product Lineups — VMAX A1 G4 DVR 8.8 High 2026-09-15
CVE-2026-66890 Use of Hard-coded Credentials in Digital Watchdog VMAX DVR and NVR Product Lineups — VMAX A1 G4 DVR 9.6 Critical 2026-09-15
CVE-2026-16141 OpenBMC IPMI Authentication Bypass via Default userKey and Stale Challenge Value — phosphor-net-ipmid 8.1 High 2026-09-15
CVE-2026-57147 praisonai-platform: default JWT signing secret 'dev-secret-change-me' enables token forgery — PraisonAI 9.8 Critical 2026-09-15
CVE-2026-90509 dromara orion-visor ExposeApiAspect.java ExposeApiAspect.beforeExposeApi hard-coded credentials — orion-visor 7.3 High 2026-09-13
CVE-2026-85083 CareCam Pro IP Cameras Use of Hard-coded Credentials — ANJIA AJL33PC0801 Firmware 6.8 Medium 2026-09-11
CVE-2026-75940 Lenovo Health Application 信任管理问题漏洞 — Health Application 9.1 Critical 2026-09-10
CVE-2026-85544 Hikvision DS-KV9503 硬件供应链问题漏洞 — DS-KV9503 6.1 Medium 2026-09-10
CVE-2026-17038 Use of Hard-coded Credentials in drEryk Gabinet — drEryk Gabinet 6.9 Medium 2026-09-10
CVE-2026-81640 Softish C6 Ear Camera and EarVision Android Application Use of Hard-coded Credentials — EarVision Android application 8.8 High 2026-09-09
CVE-2026-79731 Dell Secure Connect Gateway 信任管理问题漏洞 — Secure Connect Gateway 5.0 - Application 4.4 Medium 2026-09-09
CVE-2026-79950 Dell Secure Connect Gateway 信任管理问题漏洞 — Secure Connect Gateway 5.0 - Application 7.5 High 2026-09-09
CVE-2026-79740 Dell Secure Connect Gateway 信任管理问题漏洞 — Secure Connect Gateway 5.0 - Application 7.5 High 2026-09-09
CVE-2026-79738 Dell Secure Connect Gateway 信任管理问题漏洞 — Secure Connect Gateway 5.0 - Application 7.5 High 2026-09-09
CVE-2026-86673 ningzichun Student Management System Database Connection database.php mysqli_connect hard-coded credentials — Student Management System 7.3 High 2026-09-08
CVE-2026-80170 Dell Secure Connect Gateway 信任管理问题漏洞 — Secure Connect Gateway 5.0 - Application 6.5 Medium 2026-09-07
CVE-2026-80134 Dell Secure Connect Gateway 信任管理问题漏洞 — Secure Connect Gateway 5.0 - Application 7.7 High 2026-09-07
CVE-2026-86276 SourceCodester Syllabus-Aligned Learning Management & Examination System db.php hard-coded credentials — Syllabus-Aligned Learning Management & Examination System 7.3 High 2026-09-07
CVE-2026-86150 Tenda CP3 hostapd hard-coded credentials — CP3 4.1 Medium 2026-09-05
CVE-2026-77847 Tycon Systems TPDIN-Monitor-WEB3 Use of Hard-coded Credentials — TPDIN-Monitor-WEB3 6.5 Medium 2026-09-04
CVE-2026-5522 QRadar contains hard-coded credentials — QRadar 6.7 Medium 2026-09-04
CVE-2026-85149 Lightstar｜SmartIT Desktop Manager - Use of Hard-coded Credentials — SmartIT Desktop Manager 5.3 Medium 2026-09-04
CVE-2026-85148 Lightstar｜SmartIT Desktop Manager - Use of Hard-coded Credentials — SmartIT Desktop Manager 9.8 Critical 2026-09-04
CVE-2026-85146 Lightstar｜SmartIT Desktop Manager - Use of Hard-coded Credentials — SmartIT Desktop Manager 9.8 Critical 2026-09-04
CVE-2026-85451 MOOS core-moos through 10.4.0 Remote Process Termination via Hard-Coded Multicast Passphrase — core-moos 7.1 High 2026-09-03

Vulnerabilities classified as CWE-798 (使用硬编码的凭证) represent 684 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.