php-exploit-chain

Chains confirmed PHP audit findings into validated multi-vulnerability exploitation paths.

1.7k|238|Updated Dec 7, 2019
One-click install
npx skills add https://github.com/wgpsec/AboutSecurity --skill php-exploit-chain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: php-exploit-chain
Source: https://github.com/wgpsec/AboutSecurity/tree/main/skills/code-audit/php/php-exploit-chain
Command: npx skills add https://github.com/wgpsec/AboutSecurity --skill php-exploit-chain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After individual PHP vulnerability audits produce isolated findings, it is hard to judge real-world impact without evaluating how those vulnerabilities combine. This Skill assembles confirmed findings into complete attack chains and verifies whether each link's preconditions actually hold.

Core Features & Use Cases

  • Exploit Chain Assembly: Builds a vulnerability relationship graph mapping each finding's output capability (file write, request, data leak, code execution) to another finding's input, covering file-write-to-include RCE, SQLi-to-webshell, deserialization POP chains, SSRF-to-internal-service, info-leak-to-auth-bypass, and XSS-plus-CSRF chains.
  • Precondition Verification: Checks authentication requirements, network reachability, timing dependencies, and environment constraints such as open_basedir, disable_functions, and secure_file_priv for every chain step.
  • Composer Dependency CVE Scanning: Parses composer.lock, compares versions against Packagist Security Advisories and CVE databases, and folds dependency CVEs into the chain graph.
  • Use Case: After completing PHP injection, file, and deserialization audits on an application, use this Skill to determine whether a low-severity file write plus a controllable include path yields a Critical RCE chain, and document break points for chains that fail.

Quick Start

Evaluate the confirmed vulnerabilities from my PHP audit and assemble feasible exploit chains with severity scores and break-point analysis.

Frequently Asked Questions about php-exploit-chain

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

FAQPage Schema
How do I combine multiple PHP vulnerabilities into an exploit chain?

Build a vulnerability relationship graph mapping each confirmed finding's output capability to another finding's input, then search for the shortest path from a low-privilege entry to a high-impact sink. Verify each step's preconditions such as authentication, network reachability, and environment constraints before declaring the chain valid.

What conditions are needed for SQL injection to webshell via INTO OUTFILE?

The database user needs FILE privilege, secure_file_priv must be empty or include the web directory, the write path must be web-accessible, and the target file must not already exist since OUTFILE does not overwrite. If any condition fails, the chain breaks at that step.

How do I scan Composer dependencies for known CVEs?

Parse composer.lock to get exact versions of all direct and indirect dependencies, then compare them against Packagist Security Advisories and CVE databases like NVD or GitHub Advisory. Tools like composer audit (Composer 2.4+) or local-php-security-checker automate this check.

How is exploit chain severity calculated in a PHP audit?

Severity uses the formula Score = R * 0.40 + I * 0.35 + C * 0.25, consistent with the audit pipeline. The chain takes the weakest link's R, I, and C values, and if any step is unreachable the entire chain is considered invalid.

What should I report when an exploit chain is not feasible?

Identify the exact break point, such as secure_file_priv restricting the write path, state whether the condition could hold under other environments or configurations, and note any alternative paths that could bypass the break point.