Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
noorqureshi/web-file-uploadWeb and bug bounty

web-file-upload

⁨Turn a file upload into RCE or stored XSS/SSRF. Load on any upload: avatars, attachments, import CSV/XML, profile images, document processors, "upload your resume". Signals: multipart/form-data, filename in response, an uploads/ path, image thumbnailing, PDF/office parsing.⁩

v2026.10.14-ee0e0c54 installs+4 in 7 days27 StarsMITsynced 22 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/web-file-upload

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
jCSN01BLyu…J6aI82AQ==The CLI checks the SHA-256 and the signature before it writes a file.
Package58f8aee5…655b2a6a
58f8aee5ff62…36c1655b2a6a3 files · ⁦4.0 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/web/web-file-upload@ee0e0c5

When it applies

The app accepts a file and later stores, serves, parses, or converts it. Impact depends on what happens to the file after upload — served from webroot? passed to a parser? rendered?

Why it works

Validation is usually on the wrong signal (extension or Content-Type, both attacker-set) while the dangerous behaviour is downstream: the web server executes .php in the uploads dir, a parser follows external entities, or the file is served with an HTML content-type.

Method

Payloads & full variation set: cheatsheet.md next to this file — work the set, not the first line.

  1. Find the after-upload behaviour: where is it stored, what URL serves it, what parses it?
  2. RCE via executable extension when uploads are under a script-executing webroot: upload shell.php; if blocked, try .phtml .php5 .phar, double ext shell.php.jpg, null byte shell.php%00.jpg, case .pHp, trailing dot/space, or a polyglot (valid JPEG + PHP in a comment) with a .php name.
  3. Content-Type / magic-byte bypass: keep a real image header (GIF89a;) then payload; change the multipart Content-Type to image/png while the name stays .php.
  4. Parser-based: SVG upload → XSS/SSRF/XXE (SVG is XML+script); office/PDF → SSRF/XXE via external resources; image libraries (ImageMagick) → command exec via crafted files.
  5. Path traversal in filename: ../../var/www/html/shell.php to escape the uploads dir.

Gotchas

  • Upload succeeds but stored outside webroot / served as text/plain → no RCE; pivot to XSS/SSRF instead.
  • Random server-side filenames defeat direct access — look for a predictable/leaked path.
  • WAF strips <?php → use <?= or <script language="php">.

Verify success

Browse to the uploaded script and get command output, or the SVG/XML fires in a victim context / triggers an OOB callback.

References

PortSwigger file-upload labs; OWASP Unrestricted File Upload.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.10.14-ee0e0c5Nov 13, 2026ee0e0c558f8aee5Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login