upload-insecure-files

Identify insecure file upload paths across validation, storage, and processing boundaries.

1.6k|204|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/yaklang/hack-skills --skill upload-insecure-files
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: upload-insecure-files
Source: https://github.com/yaklang/hack-skills/tree/main/skills/upload-insecure-files
Command: npx skills add https://github.com/yaklang/hack-skills --skill upload-insecure-files

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Insecure file upload features create risk when validation, storage, and processing boundaries are misconfigured; this Skill helps testers identify and chain upload vulnerabilities from acceptance to processing and serving, including real-world scenarios and parsing pipelines referenced by SCENARIOS.md.

Core Features & Use Cases

  • Validation bypass testing across extension handling, MIME types, and content-based checks
  • Storage-path abuse and overwrite risks across multi-tenant or shared storage setups
  • Processing-chain evaluation for parsing, conversion, scanning, and rendering
  • Real-world use cases include CVE patterns like WebLogic, Tomcat, and Flink file upload chains, plus end-to-end upload-to-RCE scenarios Use Case: Simulate an upload flow in a multi-tenant web app to identify where defenses fail and how compromises propagate.

Quick Start

Run an end-to-end upload test using the companion SCENARIOS.md to validate accept, store, process, and serve stages.

Frequently Asked Questions about upload-insecure-files

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test insecure file upload vulnerabilities in a web application?

Test insecure file upload vulnerabilities by simulating upload workflows across validation, storage, and processing boundaries. It applies explicit checks for extension handling, MIME types, and server-side parsing to identify where defenses fail across accept, store, process, and serve stages.

What is file upload validation bypass testing and how does it work?

File upload validation bypass testing checks whether malicious files can evade extension, MIME type, and content-based restrictions. It evaluates the upload workflow from acceptance through server-side processing to safely reproduce real-world security testing scenarios.

Can I test upload-to-RCE scenarios using CVE patterns like WebLogic and Tomcat?

Yes, you can test upload-to-RCE scenarios using real-world CVE patterns like WebLogic, Tomcat, and Flink file upload chains. It evaluates processing-chain vulnerabilities across parsing, conversion, scanning, and rendering pipelines to identify reproducible attack paths.

Does this skill work for multi-tenant storage path abuse and overwrite risks?

Yes, it works for multi-tenant storage path abuse and overwrite risks by evaluating shared storage setups. It identifies insecure upload paths across multi-tenant storage configurations to ensure reproducible, safe security testing.

What are the limitations when testing file upload processing chains?

Limitations involve potential misconfigurations in parsing, conversion, scanning, and rendering boundaries that may not surface in isolated tests. It requires evaluating the full processing chain to accurately identify where validation bypasses and storage abuses propagate.