sc-file-upload

Detect insecure file upload vulnerabilities and generate remediation steps for web applications.

56|5|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ersinkoc/security-check --skill sc-file-upload
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sc-file-upload
Source: https://github.com/ersinkoc/security-check/tree/main/skills/sc-file-upload
Command: npx skills add https://github.com/ersinkoc/security-check --skill sc-file-upload

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Insecure file upload implementations allow attackers to upload dangerous files, bypass type checks, or place files in web-accessible locations, enabling remote code execution, stored XSS, or data exfiltration.

Core Features & Use Cases

  • Detects missing server-side file type validation and MIME-type mismatches
  • Flags unsafe upload destinations, directory permissions, and lack of file-size limits
  • Provides actionable remediation guidance for common frameworks (Node.js, PHP, Python, Java)

Quick Start

Run the skill against your codebase to identify insecure file upload endpoints and receive concrete remediation steps.

Frequently Asked Questions about sc-file-upload

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

FAQPage Schema
How do I detect insecure file upload vulnerabilities in my codebase?

Detect insecure file upload vulnerabilities by scanning back-end frameworks like Node.js, PHP, Python, and Java for missing server-side validation and unsafe MIME handling. It identifies RCE risks and generates actionable remediation steps.

Why does server-side file type validation fail to prevent remote code execution?

Server-side file type validation fails when it relies solely on client-side checks or improperly verifies MIME types, allowing malicious files to bypass filters. Validating MIME types server-side and enforcing randomized filenames prevents remote code execution.

What's the best way to secure file upload endpoints across different back-end frameworks?

Secure file upload endpoints across Node.js, PHP, Python, and Java by enforcing server-side validation, storing files outside the webroot, randomizing filenames, and applying strict size restrictions. This approach mitigates stored XSS and RCE risks.

Can I check for unsafe upload destinations and missing file-size limits in my web application?

Check for unsafe upload destinations and missing file-size limits by evaluating directory permissions and storage locations in your web application. This identifies web-accessible storage risks and enforces safe upload configurations.

Does this file upload security analysis work with Python and Java back-ends?

This file upload security analysis works with Python and Java back-ends, alongside Node.js and PHP. It evaluates upload endpoints, MIME handling, and storage configurations across these frameworks to flag insecure implementations.

When should I use randomized filenames for uploaded files?

Use randomized filenames for uploaded files when storing user-provided content to prevent attackers from predicting file paths or overwriting existing files. This practice mitigates directory traversal and remote code execution risks.