CWE · MITRE source
CWE-548Exposure of Information Through Directory Listing
The product inappropriately exposes a directory listing with an index of all the resources located inside of the directory.
Last updated: 04 July 2026 08:17 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: mostly · 2 mapping(s) from 2 framework(s): OWASP-Web 1 (mostly) · ATT&CK 1 (mostly)
OWASP Top 10 for Web (2025)
This weakness contributes to A01:2025 Broken Access Control.
NIST 800-53 r5 controls that address this weakness (3)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SC-30 | Concealment and Misdirection | SC | Directory listings and resource enumeration can be suppressed or populated with misleading entries. |
SC-38 | Operations Security | SC | Reduces exposure via directory listings or accessible files when OPSEC restricts visibility of key organizational resources. |
AU-13 | Monitoring for Information Disclosure | AU | Detects information exposure through directory listings as unauthorized disclosure. |
MITRE ATT&CK techniques this weakness enables
Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing). Drafted by Grok and spot-checked by Claude Opus 4.8.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2024-2340 UPD | 6.0 | 5.3 | 0.2800 | 2024-04-09 |
CVE-2017-6045 | 5.5 | 7.5 | 0.0168 | 2017-06-21 |
CVE-2018-10590 | 5.5 | 7.5 | 0.0171 | 2018-05-15 |
CVE-2018-14785 | 5.5 | 7.5 | 0.0221 | 2018-08-10 |
CVE-2018-16493 | 5.5 | 7.5 | 0.0176 | 2019-02-01 |
CVE-2019-5415 | 5.5 | 7.5 | 0.0169 | 2019-03-21 |
CVE-2020-8161 | 5.5 | 8.6 | 0.0359 | 2020-07-02 |
CVE-2021-21528 | 5.5 | 7.5 | 0.0095 | 2021-11-12 |
CVE-2021-27505 | 5.5 | 7.5 | 0.0096 | 2022-05-13 |
CVE-2023-51948 | 5.5 | 7.5 | 0.0071 | 2024-01-19 |
CVE-2024-22082 UPD | 5.5 | 7.5 | 0.0063 | 2024-03-20 |
CVE-2023-49979 | 5.5 | 7.5 | 0.0075 | 2024-03-21 |
CVE-2025-2038 | 5.5 | 7.3 | 0.0056 | 2025-03-06 |
CVE-2025-4909 UPD | 5.5 | 7.3 | 0.0042 | 2025-05-19 |
CVE-2025-28170 UPD | 5.5 | 7.6 | 0.0031 | 2025-07-29 |
CVE-2021-47718 | 5.5 | 7.5 | 0.0046 | 2025-12-09 |
CVE-2022-50788 | 5.5 | 7.5 | 0.0074 | 2025-12-30 |
CVE-2020-36921 | 5.5 | 7.5 | 0.0038 | 2026-01-06 |
CVE-2026-22860 UPD | 5.5 | 7.5 | 0.0066 | 2026-02-18 |
CVE-2025-32750 UPD | 5.5 | 7.5 | 0.0035 | 2026-05-20 |
CVE-2019-5437 | 3.5 | 5.3 | 0.0131 | 2019-05-10 |
CVE-2020-15081 | 3.5 | 5.3 | 0.0165 | 2020-07-02 |
CVE-2020-15790 | 3.5 | 5.3 | 0.0090 | 2020-09-09 |
CVE-2020-7858 | 3.5 | 6.8 | 0.0106 | 2021-04-22 |
CVE-2021-32510 | 3.5 | 4.3 | 0.0085 | 2021-07-07 |