php-file-upload-audit

Audit PHP source code for file upload vulnerabilities with risk levels and fixes.

386|38|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/0xShe/PHP-Code-Audit-Skill --skill php-file-upload-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: php-file-upload-audit
Source: https://github.com/0xShe/PHP-Code-Audit-Skill/tree/main/php-file-upload-audit
Command: npx skills add https://github.com/0xShe/PHP-Code-Audit-Skill --skill php-file-upload-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PHP Web applications often suffer from undetected file upload vulnerabilities that enable arbitrary uploads, path traversal, or remote code execution in web-accessible directories. This skill identifies upload entry points, save paths, filename handling, and validation logic, and outputs risk-based levels, PoC guidance, and remediation suggestions (no omissions).

Core Features & Use Cases

  • Identify upload entry points, save directories, and filename handling to reveal insecure patterns.
  • Detect arbitrary file upload, path traversal, and executable upload risks with clear evidence and actionable fixes.
  • Produce a structured report with risk levels, PoC guidance, and remediation recommendations to speed up fixes.

Quick Start

Run this skill on a PHP project to audit all file upload flows and generate a vulnerability report.

Frequently Asked Questions about php-file-upload-audit

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

FAQPage Schema
How do I audit PHP file upload vulnerabilities in my web application?

PHP file upload vulnerabilities are detected by analyzing `$_FILES` handling, `move_uploaded_file` usage, filename sanitization, and upload directory access controls. This reveals insecure patterns producing arbitrary uploads, path traversal, and remote code execution risks in web-accessible directories.

How do I check if my PHP upload script allows path traversal or arbitrary file uploads?

PHP file upload audits work by tracing upload entry points, save directories, and validation logic to reveal insecure patterns. The analysis outputs structured evidence points, PoC guidance, and risk levels to speed up remediation of arbitrary uploads and path traversal.

What is the best way to find executable upload risks in PHP source code?

The best way to find executable upload risks is auditing PHP source code for insecure `$_FILES` handling and upload directory access controls. This generates risk levels, PoC guidance, and actionable remediation suggestions for arbitrary and executable uploads.

Does this upload audit apply to pre-release PHP web application security assessments?

Yes, this upload audit applies to PHP web applications during pre-release security assessments and remediation validation. It analyzes upload flows and outputs structured traces with evidence points to validate fixes before deployment.

Can I get PoC guidance and remediation fixes for PHP file upload weaknesses?

You can get PoC guidance and remediation fixes for PHP file upload weaknesses by running an audit on the source code. It produces a structured report with risk levels, evidence traces, and actionable fixes for arbitrary uploads and path traversal.

Why does my PHP file upload implementation still allow executable uploads despite validation?

Your PHP file upload implementation might allow executable uploads due to insufficient filename sanitization or insecure upload directory access controls. Auditing the `move_uploaded_file` usage and validation logic reveals evidence points and fixes for these weaknesses.