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-2025-11643 Tomofun Furbo 360/Furbo Mini MQTT Client Certificate furbo_img hard-coded credentials — Furbo 360 3.7 Low 2025-10-12
CVE-2025-10609 Hardcoded Credentials in Logo Software's TigerWings ERP — TigerWings ERP 5.9 Medium 2025-10-03
CVE-2025-0642 Hard-coded Credentials in PosCube's Assist — Assist 6.3 Medium 2025-10-02
CVE-2025-34223 Vasion Print (formerly PrinterLogic) Insecure Installation Credentials — Print Virtual Appliance Host 9.8AI Critical AI 2025-09-29
CVE-2025-34209 Vasion Print (formerly PrinterLogic) Hardcoded GPG Private Key — Print Virtual Appliance Host 6.5AI Medium AI 2025-09-29
CVE-2025-34196 Vasion Print (formerly PrinterLogic) Hardcoded PrinterLogic CA Private Key and Hardcoded Password — Print Virtual Appliance Host 8.4AI High AI 2025-09-29
CVE-2025-11126 Apeman ID71 system.ini hard-coded credentials — ID71 9.8 Critical 2025-09-29
CVE-2025-58269 WordPress WP Project Manager Plugin <= 2.6.25 - Sensitive Data Exposure Vulnerability — WP Project Manager 5.3 Medium 2025-09-22
CVE-2025-58656 WordPress Estonian Shipping Methods for WooCommerce Plugin <= 1.7.2 - Sensitive Data Exposure Vulnerability — Estonian Shipping Methods for WooCommerce 5.3 Medium 2025-09-22
CVE-2025-58659 WordPress Helpie FAQ plugin <= 1.45 - Sensitive Data Exposure vulnerability — Helpie FAQ 5.3 Medium 2025-09-22
CVE-2025-34198 Vasion Print (formerly PrinterLogic) Shared / Hardcoded SSH Host Private Keys in Appliance Image — Print Virtual Appliance Host 9.8 - 2025-09-19
CVE-2025-34197 Vasion Print (formerly PrinterLogic) Undocumented Local Account with Hardcoded Password and Passwordless sudo — Print Virtual Appliance Host 8.4 - 2025-09-19
CVE-2024-48842 Hardcoded passwords — FLXEON 7.0 High 2025-09-17
CVE-2025-8570 BeyondCart Connector <= 3.0.1 - Missing Configuration of JWT Secret to Unauthenticated Privilege Escalation via determine_current_user Filter — BeyondCart Connector 9.8 Critical 2025-09-11
CVE-2025-55047 Baicells SPECTRA LTE-U eNB 信任管理问题漏洞 — SPECTRA LTE-U eNB 8.4 High 2025-09-09
CVE-2025-35452 Pan-Tilt-Zoom cameras default administrative credentials for web interface — PT12X-SE-xx-G3 9.8 Critical 2025-09-05
CVE-2025-35451 Pan-Tilt-Zoom cameras hard-coded default passwords with SSH and telnet enabled — PT12X-SE-xx-G3 9.8 Critical 2025-09-05
CVE-2025-55739 api: Shared OAuth Signing Key Between Different Instances — api 9.8AI Critical AI 2025-09-04
CVE-2025-9696 Use of Hard-coded Credentials in SunPower PVS6 — PVS6 8.8AI High AI 2025-09-02
CVE-2025-9806 Tenda F1202 Administrative shadow hard-coded credentials — F1202 1.9 Low 2025-09-02
CVE-2025-9778 Tenda W12 Administrative shadow hard-coded credentials — W12 1.9 Low 2025-09-01
CVE-2025-9731 Tenda AC9 Administrative shadow hard-coded credentials — AC9 2.5 Low 2025-08-31
CVE-2025-8857 Changing｜Clinic Image System - Use of Hard-coded Credentials — Clinic Image System 9.8 Critical 2025-08-29
CVE-2025-9380 FNKvision Y215 CCTV Camera Firmware passwd hard-coded credentials — Y215 CCTV Camera 7.8 High 2025-08-24
CVE-2025-9310 yeqifu carRental Druid login.html hard-coded credentials — carRental 5.3 Medium 2025-08-21
CVE-2025-9309 Tenda AC10 MD5 Hash shadow hard-coded credentials — AC10 2.5 Low 2025-08-21
CVE-2025-33100 IBM Concert Software information disclosure — Concert Software 6.2 Medium 2025-08-18
CVE-2025-7342 VM images built with Kubernetes Image Builder Nutanix or OVA providers use default credentials for Windows images if user did not override — Image Builder 7.5 High 2025-08-17
CVE-2025-9091 Tenda AC20 shadow hard-coded credentials — AC20 2.5 Low 2025-08-17
CVE-2025-8974 linlinjava litemall JSON Web Token JwtHelper.java hard-coded credentials — litemall 3.7 Low 2025-08-14

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