CWE-219: Storage of File with Sensitive Data Under Web Root

Extended Description

Besides public-facing web pages and code, products may store sensitive data, code that is not directly invoked, or other files under the web document root of the web server. If the server is not configured or otherwise used to prevent direct access to those files, then attackers may obtain this sensitive data.

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-219 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-219, Storage of File with Sensitive Data Under Web Root, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Address Storage of File with Sensitive Data Under Web Root during Implementation

MITRE associates mitigation with Implementation, and System Configuration; recorded impacts include Read Application Data; observed examples include CVE-2005-1835, CVE-2005-2217, and CVE-2002-1449. Use these source-defined anchors to turn CWE-219 into implementation, review, and verification checks for the affected component.

CWE-219: Storage of File with Sensitive Data Under Web Root — MITRE CWE

Triage CWE-219 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-219, Storage of File with Sensitive Data Under Web Root, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-219

Apply MITRE's full root-cause mapping guidance when using CWE-219, Storage of File with Sensitive Data Under Web Root. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-219 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-219, Storage of File with Sensitive Data Under Web Root. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-219: Storage of File with Sensitive Data Under Web Root?+

CWE-219: Storage of File with Sensitive Data Under Web Root is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product stores sensitive data under the web document root with insufficient access control, which might make it accessible to untrusted parties. Besides public-facing web pages and code, products may store sensitive data, code that is not directly invoked, or other files under the web document root of the web server. If the server is not configured or otherwise used to prevent direct access to those files, then attackers may obtain this sensitive data.

What are the security consequences of Storage of File with Sensitive Data Under Web Root?+

If exploited, CWE-219 (Storage of File with Sensitive Data Under Web Root) it can compromise Confidentiality, leading to outcomes such as Read Application Data.

How do you prevent or mitigate Storage of File with Sensitive Data Under Web Root?+

Recommended mitigations for CWE-219 include: Avoid storing information under the web root directory. Access control permissions should be set to prevent reading/writing of sensitive files inside/outside of the web directory.

Which programming languages are affected by Storage of File with Sensitive Data Under Web Root?+

CWE-219 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Storage of File with Sensitive Data Under Web Root?+

MITRE documents real CVEs mapped to CWE-219, including CVE-2005-1835, CVE-2005-2217, CVE-2002-1449, CVE-2002-0943 and CVE-2005-1645. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-219 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

CWE-219: Storage of File with Sensitive Data Under Web Root

Extended Description

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Phase

Description

Phase

Description

Detection Methods

Code Examples & CVEs

Observed CVE Examples (5)

CWE Relationships

Parent Weaknesses