Cyber Resilience

CWE · MITRE source

CWE-530Exposure of Backup File to an Unauthorized Control Sphere

Abstraction: Variant · CVEs in our corpus: 12

A backup file is stored in a directory or archive that is made accessible to unauthorized actors.

Often, older backup files are renamed with an extension such as .~bk to distinguish them from production files. The source code for old files that have been renamed in this manner and left in the webroot can often be retrieved. This renaming may have been performed automatically by the web server, or manually by the administrator.

Last updated: 04 July 2026 00:28 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: partial · 4 mapping(s) from 1 framework(s): ATT&CK 4 (partial)

See the full cumulative-coverage rollup →

NIST 800-53 r5 controls that address this weakness (0)AI

Control Title Family Why it addresses this CWE
No NIST controls proposed yet.

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-123305.57.50.00492025-01-09
CVE-2020-368995.57.50.00812025-12-10
CVE-2024-56462 UPD5.57.20.00462026-05-27
CVE-2025-3773 UPD3.55.50.00122025-06-26
CVE-2023-52971.53.70.00682023-09-29
CVE-2024-2364 UPD1.51.80.00332024-03-10
CVE-2024-2567 UPD1.51.80.00212024-03-17
CVE-2024-3124 UPD1.52.40.00282024-04-01
CVE-2024-3128 UPD1.52.40.00272024-04-01
CVE-2024-3430 UPD1.52.40.00222024-04-07
CVE-2026-29741.52.50.00102026-02-23
CVE-2026-135141.52.40.00132026-06-29