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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%
Buy Us a Coffee

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

559 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-2025-54872 onion-site-template tor Secrets Baked Into Image — onion-site-template 8.8AIHighAI2025-08-05
CVE-2025-37112 Hard-Coded Encryption Keys found in System — HPE Telco Network Function Virtual Orchestrator 6.0 Medium2025-07-31
CVE-2025-37111 Hard-Coded Authentication Keys found in System — HPE Telco Network Function Virtual Orchestrator 6.0 Medium2025-07-31
CVE-2014-125121 Array Networks vAPV and vxAG Default Credential Privilege Escalation — vAPV 8.8AIHighAI2025-07-31
CVE-2025-8231 D-Link DIR-890L UART Port rgbin hard-coded credentials — DIR-890L 6.8 Medium2025-07-27
CVE-2014-125115 Pandora FMS ≤ 5.0 SP2 Default Credential SQL Injection RCE — Pandora FMS 9.8 -2025-07-25
CVE-2025-31953 HCL iAutomate is affected by hardcoded credentials — iAutomate 7.1 High2025-07-24
CVE-2025-54455 SAMSUNG MagicINFO 9 Server 安全漏洞 — MagicINFO 9 Server 9.1 Critical2025-07-23
CVE-2025-54454 SAMSUNG MagicINFO 9 Server 安全漏洞 — MagicINFO 9 Server 9.1 Critical2025-07-23
CVE-2025-4130 Hardcoded Credentials in PAVO Inc.'s PAVO Pay — PAVO Pay 7.5 High2025-07-21
CVE-2025-4570 ASUS MyASUS 安全漏洞 — MyASUS 7.5 -2025-07-21
CVE-2025-4569 ASUS MyASUS 安全漏洞 — MyASUS 7.5 -2025-07-21
CVE-2025-4049 Hardcoded SQLite password in FARA — FARA 9.8 -2025-07-21
CVE-2025-6982 Hardcoded DES Decryption Keys in TP-Link Archer C50 V3/V4/V5 and C20 V5 — Archer C50 V3 7.5AIHighAI2025-07-16
CVE-2025-53754 Hard-coded Credentials Vulnerability in Digisol DG-GR6821AC Router — XPON ONU Wi-Fi Router (DG-GR6821AC) 6.8AIMediumAI2025-07-16
CVE-2025-53842 ZEXELON ZWX-2000CSW2-HN和ZEXELON ZWX-2000CS2-HN 信任管理问题漏洞 — ZWX-2000CSW2-HN 9.8AICriticalAI2025-07-16
CVE-2025-7564 LB-LINK BL-AC3600 shadow hard-coded credentials — BL-AC3600 7.8 High2025-07-14
CVE-2025-7503 Shenzhen Liandian Communication Technology V380 IP Camera 安全漏洞 — V380 IP Camera / AppFHE1_V1.0.6.0 9.8AICriticalAI2025-07-11
CVE-2025-7401 Premium Age Verification / Restriction for WordPress <= 3.0.2 - Unauthenticated Arbitrary File Read and Write via remote_tunnel.php — Premium Age Verification / Restriction for WordPress 9.8 Critical2025-07-11
CVE-2025-5023 Mitsubishi Electric PV-DR004J 信任管理问题漏洞 — PV-DR004J 7.1 High2025-07-10
CVE-2025-49551 ColdFusion | Use of Hard-coded Credentials (CWE-798) — ColdFusion 8.8 High2025-07-08
CVE-2025-20309 Cisco Unified Communications Manager Static SSH Credentials Vulnerability — Cisco Unified Communications Manager 10.0 Critical2025-07-02
CVE-2025-34034 5VTechnologies Blue Angel Software Suite Hardcoded Credentials — Blue Angel Software Suite 9.8AICriticalAI2025-06-24
CVE-2025-34509 Sitecore XM and XP Hardcoded Credentials — Experience Manager 7.5 High2025-06-17
CVE-2025-35940 Hard-coded ArchiverSpaApi JWT Signing Key — Archiver 8.1 High2025-06-10
CVE-2025-5751 WOLFBOX Level 2 EV Charger Management Card Hard-coded Credentials Authentication Bypass Vulnerability — Level 2 EV Charger 6.8AIMediumAI2025-06-06
CVE-2025-3321 Use of Hard-coded Credentials in OnlineSuite — OnlineSuite 7.8AIHighAI2025-06-06
CVE-2025-5379 NuCom NC-WR744G Console Application hard-coded credentials — NC-WR744G 4.3 Medium2025-05-31
CVE-2025-4633 Default Credentials — Airpointer 6.5 Medium2025-05-30
CVE-2025-48491 Project AI API Key Exposure in Source Code — project-ai 7.5AIHighAI2025-05-30

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