File and Path Handling · payload topic
Upload Insecure Files
20 passages · 10 code blocks
Out of date: the sync last ran 3 hours ago. Newer CVEs and scores may be missing from the map.
Every mark is a titled passage of this topic's pages, in reading order; the brighter ones carry code. For testing systems you own or are authorised to test, and for defending them. Nothing here is run by this page.
Open Upload Insecure Files on GitHubUploaded files may pose a significant risk if not handled correctly. A remote attacker could send a multipart/form-data POST request with a specially-crafted filename or mime type and execute arbitrary code.
Source: PayloadsAllTheThings. From PayloadsAllTheThings by Swissky and contributors. MIT License, Copyright (c) 2019 Swissky.
Every one of the 20 is a mark on the map. Named now: 1 to 20, reading order first.
- .htaccess
- AddType Directive
- Self Contained .htaccess
- Polyglot .htaccess
- Upload Insecure Files
- Methodology
- Defaults Extensions
- Upload Tricks
- Filename Vulnerabilities
- Picture Compression
- Picture Metadata
- Configuration Files
- Apache: .htaccess
- WSGI: uwsgi.ini
- Dependency Manager
- Python Path File
- CVE - ImageMagick
- CVE-2016–3714 - ImageTragik
- CVE-2022-44268
- CVE - FFMpeg HLS
Zoom in on the map and the dots under the middle of it are named where they are.
Data as of 2026-11-14. CVE List through 2026-11-14 · EPSS of 2026-11-13 · CISA KEV checked 2026-11-14. Source: PayloadsAllTheThings by Swissky and contributors, MIT License. For authorised testing only.