Security pattern / case archive

Dangerous File Upload

An upload accepts a filename or file type that the web server can later execute or interpret unsafely.

Common discovery signals
  • The upload directory is public and executable extensions are not handled consistently.
  • A static multi-extension control and an executable-extension test produce different responses.
Safe validation approach

Use a small fixed proof reader, compare storage with execution, and stop after the first confirmed result.

Related classifications

Related entries

Archive connections

Connected case files

01 record
CASE-015WEBVERSE
Connected evidence

Owners

Stored XSS / Dangerous File Upload

Owners chained Stored XSS in the staff message viewer with an unsafe avatar upload. The staff browser kept its own session, .php and .php.jpg provided the controls, and .phtml returned the redacted lab proof.