php-file-read-audit

Map PHP file read and path traversal vulnerabilities with source-to-sink evidence.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PHP Web 源码任意文件读取/路径穿越审计工具。识别文件读取 Sink,追踪路径来源与校验逻辑,输出可利用性分级、PoC 与修复建议(禁止省略)。

Core Features & Use Cases

  • 识别常见文件读取和包含风险点(read/include/require 等)及路径穿越场景
  • 跟踪数据流,给出源→汇的证据链和可控性分析
  • 输出修复建议与可验证的 PoC 设计思路

Quick Start

Run the PHP file-read-audit workflow against a target PHP project to detect file read and path traversal weaknesses and generate remediation guidance.

Frequently Asked Questions about php-file-read-audit

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

FAQPage Schema
How do I audit PHP source code for file read and path traversal vulnerabilities?

Audit PHP file read and path traversal vulnerabilities by applying static analysis to locate sinks like read, include, and require, trace input sources to execution boundaries, and produce verified data flow evidence with controllability analysis.

What is the best way to trace PHP include and require sinks to their input sources?

Tracing PHP include and require sinks requires mapping the complete data flow from source to sink, verifying controllability at execution boundaries, and validating stream wrappers to identify path traversal gaps accurately.

How do I generate a PoC and remediation guidance for PHP path traversal findings?

Generate a PoC and remediation guidance for PHP path traversal by analyzing validation gaps along the verified data flow, assessing exploitability levels, and outputting targeted fix recommendations to block unsafe file reads.

Does static analysis detect stream wrapper exploits in PHP file read operations?

Static analysis detects stream wrapper exploits in PHP file read operations by mapping include and require statements, identifying unvalidated input sources, and tracing controllable data flow to the execution sink.

Can I assess exploitability levels for file read vulnerabilities without dynamic testing?

Assess exploitability levels for file read vulnerabilities without dynamic testing by evaluating static validation gaps, verifying controllability of the source-to-sink data flow, and checking execution boundaries within the PHP codebase.