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

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

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

626 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 ControlBypass 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, OtherRead 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 DesignFor 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 DesignFor 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 DesignIf 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 DesignFor 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 DesignFor 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 IDTitleCVSSSeverityPublished
CVE-2026-67568 Mira Hormone Monitor, Mira Android App Use of Hard-coded Credentials — Mira Firmware 9.1 Critical2026-08-11
CVE-2026-69102 MaxKey Hard-coded JWT Secret Unauthorized Access via /login/jwt/trust — MaxKey 9.8 Critical2026-08-11
CVE-2026-58245 Hard-coded Credentials in SAP Advanced Planning and Optimization (Model Mix Planning) — SAP Advanced Planning and Optimization (Model Mix Planning) 3.8 Low2026-08-11
CVE-2025-13293 Backdoor / default root credentials — TBEA TLogger (TBEA Communication Box 3rd Generation) 9.3 Critical2026-08-10
CVE-2026-6374 Hardcoded Credentials in Zyxel WAH7601 Router — WAH7601 7.3 High2026-08-10
CVE-2026-49007 Information leakage vulnerability in ZTE F689 product — F689 7.5 High2026-08-07
CVE-2026-71238 DjangoCRM - Hardcoded Django SECRET_KEY Enables Session and CSRF Token Forgery — django-crm 9.1 Critical2026-08-05
CVE-2026-48031 Go Restful API Boilerplate: Hardcoded JWT Secret "random" Allows Token Forgery — go-base 9.1 Critical2026-08-03
CVE-2025-15628 Hardcoded Certificates in TP-Link Omada Device Communications — Omada Gateways 8.2 High2026-08-03
CVE-2026-65313 Use of hard-coded VNC credentials in the engineering-workstation provisioning — HIPASE-250 8.1 High2026-07-31
CVE-2026-18452 Rich Source｜DMS+ (Non-Mobile) - Use of Hard-coded Credentials — DMS+ (Non-Mobile) 10.0 Critical2026-07-31
CVE-2026-13463 Due to use of IBM Storage Protect, IBM Cloud Pak System is affected by vulnerability [] — Cloud Pak System 7.5 High2026-07-28
CVE-2026-12001 Hardcoded Credential Vulnerability in Multiple TP-Link Router Models — TL-WR850N v3 5.2 Medium2026-07-27
CVE-2026-55579 Pheditor: Hardcoded default password 'admin' with no forced change enables full application compromise — pheditor 9.8 Critical2026-07-27
CVE-2025-59180 Use of Hard-coded Credentials Vulnerability — Packet Core Controller (PCC) 5.1 Medium2026-07-27
CVE-2026-8983 Backdoor Authentication Token — MaxiCharger Single--2026-07-21
CVE-2026-8982 Hard-coded / Backdoor Accounts — MaxiCharger Single--2026-07-21
CVE-2026-13446 Langflow is affected by remote code execution, denial of service, path traversal, and exposed credentials due to multiple unauthenticated and insufficiently authorized API endpoints — Langflow OSS 9.8 Critical2026-07-17
CVE-2026-45336 HireFlow: Use of Hard-coded Credentials — HireFlow 10.0 Critical2026-07-16
CVE-2026-49352 9Router: Hardcoded Default fallback JWT Secret Allows Authentication Bypass — 9router 9.8 Critical2026-07-15
CVE-2026-61684 FastGPT: Unauthenticated cross-tenant data access via forgeable plugin-invoke JWT (default INVOKE_TOKEN_SECRET='token') — FastGPT--2026-07-15
CVE-2026-14807 PROG MIS｜ERP App - Use of Hard-coded Credentials — ERP App 9.8 Critical2026-07-06
CVE-2026-13768 Gardyn IoT Hub Use of Hard-coded Credentials — Gardyn Home Firmware 10.0 Critical2026-07-02
CVE-2026-13728 WatchGuard Firebox Hardcoded Fallback Encryption Key in Access Portal Resource Credential Database — Fireware OS 5.9 Medium2026-07-02
CVE-2026-7839 UltraVNC repeater ships hardcoded default admin password allowing unauthenticated admin access — UltraVNC 9.1 Critical2026-07-01
CVE-2026-50110 Use of Hard-coded Credentials in StoneFly Storage Concentrator — Storage Concentrator 9.2 Critical2026-06-30
CVE-2026-56278 Flowise - Session Hijacking via Weak Default Express Session Secret — Flowise 9.1 Critical2026-06-30
CVE-2026-31928 Daktronics Controller Firmware Use of Hard-coded Credentials — VFC-DMP-5000 8.1 High2026-06-26
CVE-2026-56269 Flowise - Weak Default Token Hash Secret in JWT Token Encryption — Flowise 4.6 Medium2026-06-24
CVE-2026-12628 Hardcoded credential in the IBM Storage Protect Snapshot For Windows leads to unauthorized access to system — Storage Protect Client 9.1 Critical2026-06-22

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