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

What is CWE-530?

CWE-530 is Exposure of Backup File to an Unauthorized Control Sphere. The flaw arises when a backup file is stored in a directory or archive that is made accessible to unauthorized actors. The database currently holds 3 vulnerabilities mapped to CWE-530 and none of them are in the CISA Known Exploited Vulnerabilities catalog.

OWASP Top 10 Rank-
Related CVES (365 days)3
AbstractionVariant
Likelihood of exploit-

Vulnerabilities mapped to CWE-530

3 vulnerabilities200% increase year over year

No data

No vulnerability data in CISA KEV for CWE-530

Official definition

ByMitre CWE

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.

Characteristics

Modes of introduction

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

Common consequences

ImpactScopeExplanation
Read Application DataConfidentialityAt a minimum, an attacker who retrieves this file would have all the information contained in it, whether that be database calls, the format of parameters accepted by the application, or simply information regarding the architectural structure of your site.

Risk mitigations

  1. PolicyRecommendations include implementing a security policy within your organization that prohibits backing up web application source code in the webroot.

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

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.