Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
CWE-260 Base Incomplete
Password in Configuration File
This vulnerability occurs when an application stores sensitive passwords directly within a configuration file, making them easily readable to anyone with access to that file.
Definition
What is CWE-260?
This vulnerability occurs when an application stores sensitive passwords directly within a configuration file, making them easily readable to anyone with access to that file.
Storing passwords in plain text within config files, such as .env, .properties, XML, or YAML files, is a critical security misstep. These files are often committed to version control, deployed with the application, or left in accessible directories, exposing the credentials to developers, system administrators, or even attackers who gain basic access to the system. The core problem is that configuration files are designed for settings, not for safeguarding secrets.
An attacker who discovers this file can immediately steal the password to impersonate the application, often gaining the same level of access to databases, external APIs, or administrative systems. In some cases, if the file has write permissions, they could even change the password to one they control, locking out the legitimate application and taking full control of the dependent service. This single flaw can lead to complete system compromise, data breaches, and unauthorized actions performed under the application's identity.
Real-world impact
Real-world CVEs caused by CWE-260
-
A continuous delivery pipeline management tool stores an unencypted password in a configuration file.
How attackers exploit it
Step-by-step attacker path
- 1
Below is a snippet from a Java properties file.
- 2
Because the LDAP credentials are stored in plaintext, anyone with access to the file can gain access to the resource.
- 3
The following examples show a portion of properties and configuration files for Java and ASP.NET applications. The files include username and password information but they are stored in cleartext.
- 4
This Java example shows a properties file with a cleartext username / password pair.
- 5
The following example shows a portion of a configuration file for an ASP.Net application. This configuration file includes username and password information for a connection to a database but the pair is stored in cleartext.
Vulnerable code example
Vulnerable Java
Below is a snippet from a Java properties file.
webapp.ldap.username = secretUsername
webapp.ldap.password = secretPassword Secure code example
Secure pseudo
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
const safe = validateAndEscape(input);
return executeWithGuards(safe);
} What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Prevention checklist
How to prevent CWE-260
- Architecture and Design Avoid storing passwords in easily accessible locations.
- Architecture and Design Consider storing cryptographic hashes of passwords as an alternative to storing in plaintext.
Detection signals
How to detect CWE-260
CWE-260
Don't catalog this weakness. Prove it's reachable.
Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.
Frequently asked questions What is CWE-260?
How serious is CWE-260?
What languages or platforms are affected by CWE-260?
How can I prevent CWE-260?
How does Plexicus detect and fix CWE-260?
Where can I learn more about CWE-260?
Frequently asked questions
What is CWE-260?
This vulnerability occurs when an application stores sensitive passwords directly within a configuration file, making them easily readable to anyone with access to that file.
How serious is CWE-260?
MITRE has not published a likelihood-of-exploit rating for this weakness. Treat it as medium-impact until your threat model proves otherwise.
What languages or platforms are affected by CWE-260?
MITRE has not specified affected platforms for this CWE — it can apply across most application stacks.
How can I prevent CWE-260?
Avoid storing passwords in easily accessible locations. Consider storing cryptographic hashes of passwords as an alternative to storing in plaintext.
How does Plexicus detect and fix CWE-260?
Plexicus's SAST engine matches the data-flow signature for CWE-260 on every commit. When a match is found, our Codex Remedium agent opens a fix PR with the corrected code, tests, and a one-line summary for the reviewer.
Where can I learn more about CWE-260?
MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/260.html. You can also reference OWASP and NIST documentation for adjacent guidance.
Related weaknesses
Weaknesses related to CWE-260
CWE-522 Parent
Insufficiently Protected Credentials
This vulnerability occurs when an application handles sensitive credentials like passwords or API keys in an insecure way, making them…
CWE-256 Sibling
Plaintext Storage of a Password
This vulnerability occurs when an application stores user passwords as readable text instead of using secure, one-way hashing. This…
CWE-257 Sibling
Storing Passwords in a Recoverable Format
This vulnerability occurs when an application stores user passwords in a format that can be easily reversed or decrypted back to their…
CWE-261 Sibling
Weak Encoding for Password
Using simple encoding like Base64 to hide a password provides no real security, as it can be easily reversed.
CWE-523 Sibling
Unprotected Transport of Credentials
This vulnerability occurs when a login page or authentication system transmits user credentials (like usernames and passwords) over a…
CWE-549 Sibling
Missing Password Field Masking
This vulnerability occurs when an application fails to hide password characters as they are typed, making them visible to anyone who can…
CWE-13 Child
ASP.NET Misconfiguration: Password in Configuration File
This vulnerability occurs when an ASP.NET application stores passwords or other sensitive credentials in plaintext within configuration…
CWE-258 Child
Empty Password in Configuration File
This vulnerability occurs when a configuration file, script, or application uses an empty string as a password, effectively disabling…
CWE-555 Child
J2EE Misconfiguration: Plaintext Password in Configuration File
A J2EE application insecurely stores an unprotected password within a configuration file.
Resources
Further reading
- MITRE — official CWE-260 https://cwe.mitre.org/data/definitions/260.html
- Seven Pernicious Kingdoms: A Taxonomy of Software Security Errors https://samate.nist.gov/SSATTM_Content/papers/Seven%20Pernicious%20Kingdoms%20-%20Taxonomy%20of%20Sw%20Security%20Errors%20-%20Tsipenyuk%20-%20Chess%20-%20McGraw.pdf
Ready to validate what matters?
Ready to validate what matters?
Plexicus is Proof-Driven AppSec: validated findings, contextual understanding, and reviewed remediation — anchored in evidence, scoped with you.