Skip to content
StrikeOps

Unrestricted File Upload

HighTypical severity Web applications and APIsCWE-434ATT&CK T1505.003

01Description

The application's upload feature did not adequately restrict the type, content or storage location of uploaded files.

02Impact

Depending on where files are stored and served, an attacker may upload a script that the server executes, giving remote control of the server, or upload HTML and SVG files that run script in other users' browsers.

03Severity

Typically

High

Typically High. Critical if uploaded files can be executed on the server (a web shell). Medium if uploads are stored safely but allow stored XSS through HTML or SVG files.

04How to verify

  1. 1Upload files with dangerous extensions, double extensions and mismatched content types using benign content.
  2. 2Determine where uploaded files are stored and whether they are served from the application's domain or executed.
  3. 3Confirm execution only with a harmless marker, never a functional web shell outside agreed scope.

Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.

05Remediation

  1. 1Validate file type by content on the server against an allow-list.
  2. 2Store uploads outside the web root or in object storage, served from a separate domain.
  3. 3Rename uploaded files and set safe Content-Type and Content-Disposition headers.
  4. 4Scan uploads for malware.

06References

Draft findings like this from your own evidence

Book a demo
Book a demo