CWE-552: Files or Directories Accessible to External Parties

What is CWE-552?

CWE-552 is Files or Directories Accessible to External Parties. The flaw arises when the product makes files or directories accessible to unauthorized actors, even though they should not be.

OWASP TOP 10:2025 RANK1 — A01:2025 — Broken Access Control
Related CVES (365 days)-
AbstractionBase
Likelihood of exploit-

No data

No vulnerability data for CWE-552

No data

No vulnerability data in CISA KEV for CWE-552

Official definition

ByMitre CWE

The product makes files or directories accessible to unauthorized actors, even though they should not be.

Web servers, FTP servers, and similar servers may store a set of files underneath a "root" directory that is accessible to the server's users. Applications may store sensitive files underneath this root without also using access control to limit which users may request those files, if any. Alternately, an application might package multiple files or directories into an archive file (e.g., ZIP or tar), but the application might not exclude sensitive files that are underneath those directories.

In cloud technologies and containers, this weakness might present itself in the form of misconfigured storage accounts that can be read or written by a public or anonymous user.

Characteristics

Modes of introduction

  • Architecture and Design
  • Implementation: OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.
  • Operation: OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.

Common consequences

ImpactScopeExplanation
Read Files or Directories, Modify Files or DirectoriesConfidentiality, Integrity-

Risk mitigations

  1. Implementation, System Configuration, OperationWhen storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to disable public access.

Detection methods

MethodApproachEffectiveness
Automated Static AnalysisAutomated 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.)High

Representative vulnerabilities

Below are representative vulnerabilities related to this CWE, prioritized by severity.

Sources (2)

CWE™ Program, operated by The MITRE Corporation. Copyright © 2006–2026, The MITRE Corporation. The MITRE Corporation hereby grants you a non-exclusive, royalty-free license to use CWE for research, development, and commercial purposes. CWE Terms of Use.

Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.