---
title: "CWE-552: Files or Directories Accessible to External Parties"
url: https://radicalnotion.ai/cwe/cwe-552
type: cwe
description: "The product makes files or directories accessible to unauthorized actors, even though they should not be."
updated: 2026-11-10
source: RadicalNotion.AI
license: CC BY-NC 4.0 (https://creativecommons.org/licenses/by-nc/4.0/)
---

# CWE-552: Files or Directories Accessible to External Parties

- **Abstraction:** Base
- **Structure:** Simple
- **Status:** Draft
- **CVEs with this as primary weakness:** 458
- **Of those, in CISA KEV:** 5
- **New in 2026:** 109
- **CWE catalog version:** 4.21

## Description

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.

## Modes of introduction

| Phase | Note |
| --- | --- |
| 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. |
| System Configuration | 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. |

## Applicable platforms

**Technologies:** Cloud Computing (Often)

## Common consequences

| Scope | Impact | Note |
| --- | --- | --- |
| Confidentiality, Integrity | Read Files or Directories, Modify Files or Directories | - |

## Potential mitigations

### Implementation, System Configuration, Operation

When 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

### Automated Static Analysis

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.)

Effectiveness: High

## Demonstrative examples

### Example 1

The following Azure command updates the settings for a storage account:

Bad code:

```shell
az storage account update --name <storage-account> --resource-group <resource-group> --allow-blob-public-access true
```

Good code:

```shell
az storage account update --name <storage-account> --resource-group <resource-group> --allow-blob-public-access false
```

### Example 2

The following Google Cloud Storage command gets the settings for a storage account named 'BUCKET\_NAME':

Informative code:

```shell
gsutil iam get gs://BUCKET_NAME
```

Bad code:

```json
{
    "bindings":[{
        "members":[
            "projectEditor: PROJECT-ID",
            "projectOwner: PROJECT-ID"
        ],
        "role":"roles/storage.legacyBucketOwner"
    },
    {
        "members":[
            "allUsers",
            "projectViewer: PROJECT-ID"
            ],
            "role":"roles/storage.legacyBucketReader"
        }
    ]
}
```

Good code:

```shell
gsutil iam ch -d allUsers gs://BUCKET_NAME
gsutil iam ch -d allAuthenticatedUsers gs://BUCKET_NAME
```

## Observed examples

| CVE | Description |
| --- | --- |
| CVE-2005-1835 | Data file under web root. |

## Real CVEs with this weakness (sample of 12 of 458)

| CVE | Title | Severity | CVSS | EPSS | CISA KEV | Published |
| --- | --- | --- | --- | --- | --- | --- |
| CVE-2026-21589 | Atlassian Multiple Products Files or Directories Accessible to External Parties Vulnerability | critical | 9.3 | - | Yes | 2026-10-05 |
| CVE-2020-17519 | Apache Flink directory traversal attack: reading remote files through the REST API | critical | 9.2 | - | Yes | 2021-01-05 |
| CVE-2025-11371 | Gladinet CentreStack and TrioFox Local File Inclusion Flaw | high | 8.7 | - | Yes | 2025-10-09 |
| CVE-2017-16651 | Roundcube Webmail File Disclosure Vulnerability | high | 8.3 | - | Yes | 2017-11-09 |
| CVE-2016-3715 | ImageMagick Arbitrary File Deletion Vulnerability | high | 7.2 | - | Yes | 2016-05-05 |
| CVE-2026-71379 | Toptech TMS7 and TopHAT Files or Directories Accessible to External Parties | critical | 10.0 | - | No | 2026-09-29 |
| CVE-2025-41240 | Mounted Kubernetes Secrets under a predictable path located within the web server document root | critical | 10.0 | - | No | 2025-07-24 |
| CVE-2024-56731 | Gogs deletion of internal files allows remote command execution | critical | 10.0 | - | No | 2025-06-24 |
| CVE-2026-76531 | Files or Directories Accessible to External Parties in Splunk SOAR | critical | 9.9 | - | No | 2026-10-21 |
| CVE-2024-39931 | Gogs allows deletion of internal files | critical | 9.9 | - | No | 2024-07-04 |
| CVE-2021-32008 | Logged-in Administrator may get unrestricted file system access | critical | 9.9 | - | No | 2022-03-04 |
| CVE-2021-43821 | Files Accessible to External Parties in Opencast | critical | 9.9 | - | No | 2021-12-14 |

## Related attack patterns (CAPEC)

- [CAPEC-150](https://radicalnotion.ai/capec/capec-150): Collect Data from Common Resource Locations
- [CAPEC-639](https://radicalnotion.ai/capec/capec-639): Probe System Files

## Related weaknesses

| Relationship | CWE | Name |
| --- | --- | --- |
| Parent | [CWE-285](https://radicalnotion.ai/cwe/cwe-285) | Improper Authorization |
| Parent | [CWE-668](https://radicalnotion.ai/cwe/cwe-668) | Exposure of Resource to Wrong Sphere |
| Child | [CWE-219](https://radicalnotion.ai/cwe/cwe-219) | Storage of File with Sensitive Data Under Web Root |
| Child | [CWE-220](https://radicalnotion.ai/cwe/cwe-220) | Storage of File With Sensitive Data Under FTP Root |
| Child | [CWE-527](https://radicalnotion.ai/cwe/cwe-527) | Exposure of Version-Control Repository to an Unauthorized Control Sphere |
| Child | [CWE-528](https://radicalnotion.ai/cwe/cwe-528) | Exposure of Core Dump File to an Unauthorized Control Sphere |
| Child | [CWE-529](https://radicalnotion.ai/cwe/cwe-529) | Exposure of Access Control List Files to an Unauthorized Control Sphere |
| Child | [CWE-530](https://radicalnotion.ai/cwe/cwe-530) | Exposure of Backup File to an Unauthorized Control Sphere |
| Child | [CWE-539](https://radicalnotion.ai/cwe/cwe-539) | Use of Persistent Cookies Containing Sensitive Information |
| Child | [CWE-553](https://radicalnotion.ai/cwe/cwe-553) | Command Shell in Externally Accessible Directory |

## Taxonomy mappings

| Taxonomy | Entry | Id | Fit |
| --- | --- | --- | --- |
| OWASP Top Ten 2004 | Insecure Configuration Management | A10 | CWE More Specific |
| CERT C Secure Coding | Ensure that file operations are performed in a secure directory | FIO15-C | - |

## Frequently asked questions

### What is CWE-552?

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

### What CVEs are caused by CWE-552?

458 recorded CVEs are attributed to CWE-552, including CVE-2026-21589, CVE-2020-17519 and CVE-2025-11371. 5 are listed in CISA's Known Exploited Vulnerabilities (KEV) catalog.

### Is CWE-552 part of the OWASP Top 10?

CWE-552 maps to OWASP Top Ten 2004: Insecure Configuration Management (A10) in the OWASP security taxonomy.

### How do you prevent CWE-552?

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

### How is CWE-552 detected?

Automated Static Analysis: 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.)

### What are the consequences of CWE-552?

Exploiting CWE-552 can lead to: Read Files or Directories, Modify Files or Directories.

### Is CWE-552 actively exploited?

Yes. 5 CWE-552 vulnerabilities are in CISA's KEV catalog of actively exploited flaws, out of 458 recorded CVEs.

Primary source: [MITRE CWE](https://cwe.mitre.org/data/definitions/552.html)

---

Source: [RadicalNotion.AI](https://radicalnotion.ai/cwe/cwe-552). Licensed CC BY-NC 4.0; attribute RadicalNotion.AI and link the source page when you reuse this data.
