CWE · MITRE source
CWE-313Cleartext Storage in a File or on Disk
The product stores sensitive information in cleartext in a file, or on disk.
The sensitive information could be read by attackers with access to the file, or with physical or administrator access to the raw disk. Even if the information is encoded in a way that is not human-readable, certain techniques could determine which encoding is being used, then decode the information.
Last updated: 15 October 2026 14:21 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: full · 4 mapping(s) from 4 framework(s): STIG oracle linux 8 1 (full) · STIG oracle linux 9 1 (mostly) · STIG rhel 8 1 (mostly) · STIG rhel 9 1 (mostly)
OWASP Top 10 for Web (2025)
This weakness contributes to A06:2025 Insecure Design.
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
NIST 800-53 r5 controls PROPOSED for this weakness (1)AI-assisted
These are model PROPOSALS, not graded mappings. They come
from controls_to_cwe_proposals, which carries no grade field at
all; across the CWE pages 1,540 of 1,722 such associations (89%) have never
been graded by anything. The heading said “address” until
2026-09-29, which asserted a relationship the data does not carry.
Graded cross-walks are on the framework map, not here.
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SC-28 | Protection of Information at Rest | SC | graded full Mandating protection of files and disk-stored data at rest prevents the specific weakness of cleartext storage on disk or in files. |
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2016-6538 UPD | 6.8 | 8.8 | 0.0106 | 2018-07-06 |
CVE-2025-5098 UPD | 6.8 | 9.1 | 0.0030 | 2025-05-23 |
CVE-2016-6546 UPD | 5.8 | 7.8 | 0.0041 | 2018-07-13 |
CVE-2016-6547 UPD | 5.8 | 7.8 | 0.0041 | 2018-07-13 |
CVE-2026-52783 | 5.7 | 8.2 | 0.0020 | 2026-06-26 |
CVE-2025-4397 UPD | 4.9 | 6.8 | 0.0013 | 2026-05-07 |
CVE-2025-64305 UPD | 4.8 | 6.5 | 0.0014 | 2026-01-07 |
CVE-2026-24349 UPD | 4.8 | 7.1 | 0.0006 | 2026-06-09 |
CVE-2026-14663 UPD | 4.8 | 6.5 | 0.0010 | 2026-08-13 |
CVE-2025-36154 UPD | 4.5 | 6.2 | 0.0010 | 2025-12-24 |
CVE-2019-19291 UPD | 4.4 | 5.3 | 0.0075 | 2020-03-10 |
CVE-2024-20448 | 4.4 | 6.3 | 0.0012 | 2024-10-02 |
CVE-2026-5531 UPD | 4.4 | 5.3 | 0.0032 | 2026-04-05 |
CVE-2023-4066 UPD | 4.2 | 5.5 | 0.0016 | 2023-09-27 |
CVE-2018-10622 UPD | 4.1 | 5.2 | 0.0036 | 2018-08-10 |
CVE-2024-6785 | 4.1 | 5.5 | 0.0011 | 2024-09-21 |
CVE-2024-30406 UPD | 4.0 | 5.5 | 0.0014 | 2024-04-12 |
CVE-2023-35699 UPD | 3.9 | 5.3 | 0.0020 | 2023-07-10 |
CVE-2024-5916 | 3.6 | 4.4 | 0.0025 | 2024-08-14 |
CVE-2026-6598 | 3.6 | 4.3 | 0.0024 | 2026-04-20 |
CVE-2026-6796 | 3.6 | 4.3 | 0.0023 | 2026-04-21 |
CVE-2024-38280 UPD | 3.5 | 4.6 | 0.0015 | 2024-06-13 |
CVE-2024-49762 UPD | 3.4 | 4.6 | 0.0014 | 2024-10-24 |
CVE-2026-90842 | 3.2 | 3.7 | 0.0031 | 2026-09-15 |
CVE-2026-5769 | 3.1 | 4.1 | 0.0007 | 2026-10-08 |