phpinfo-to-rce

Analyze phpinfo output to identify RCE vectors and file upload paths.

1.1k|191|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/uphiago/recon-skills --skill phpinfo-to-rce
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phpinfo-to-rce
Source: https://github.com/uphiago/recon-skills/tree/main/recon/phpinfo-to-rce
Command: npx skills add https://github.com/uphiago/recon-skills --skill phpinfo-to-rce

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the need for blind exploit testing when an exposed phpinfo page is discovered during reconnaissance, quickly determining if the target is vulnerable to remote code execution via available exec functions or bypass techniques.

Core Features & Use Cases

  • PHPInfo Analysis: Parses exposed phpinfo output to identify critical directives like disable_functions, allow_url_fopen, and PHP version to assess RCE viability.
  • Bypass Detection: Checks for common disable_functions bypass vectors including LD_PRELOAD (via putenv) and FFI for PHP 7.4+ environments.
  • Upload Vector Discovery: Scans for common file upload paths including WordPress XMLRPC wp.uploadFile, open registration forms, contact forms, and plugin-specific upload endpoints.
  • Use Case: A penetration tester who discovers an exposed info.php on a WordPress e-commerce target can use this Skill to quickly confirm RCE possibility and identify the optimal upload vector to deliver a webshell.

Quick Start

Use the phpinfo-to-rce skill to analyze the exposed phpinfo page at https://your-target.com/info.php, confirm if exec functions are available or viable bypasses exist, and locate a file upload vector to deliver a webshell for code execution.

Frequently Asked Questions about phpinfo-to-rce

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

FAQPage Schema
How can I exploit an exposed phpinfo page to achieve remote code execution?

An exposed phpinfo page can be chained to remote code execution by parsing critical directives like disable_functions and allow_url_fopen to identify available exec functions or bypass techniques, then locating file upload paths to deliver a webshell.

What bypass techniques can I use when disable_functions blocks exec functions in PHP?

When disable_functions restricts standard exec functions, you can attempt bypass vectors like LD_PRELOAD via putenv or FFI in PHP 7.4+ environments to regain code execution capabilities on the target server.

How do I find file upload vectors on a WordPress target after reviewing phpinfo?

You can discover file upload vectors by scanning for WordPress XMLRPC wp.uploadFile, open registration forms, contact forms, and plugin-specific upload endpoints to deliver a webshell payload for code execution.

Can I use phpinfo output to determine if a web server is vulnerable to RCE?

Yes, parsing phpinfo output reveals the PHP version, enabled exec functions, and critical security directives like disable_functions and allow_url_fopen, allowing you to quickly assess the viability of remote code execution.

Does this RCE exploit chain work on non-WordPress environments?

While the primary focus is on WordPress environments and common vectors like XMLRPC wp.uploadFile, the core mechanism of parsing phpinfo for exec functions and bypass techniques applies to any web server exposing a phpinfo endpoint.

What specific PHP directives should I look for in phpinfo to plan a webshell upload?

You should parse phpinfo for disable_functions to check for bypass needs, allow_url_fopen to understand remote inclusion capabilities, and the PHP version to determine if FFI bypass vectors are available.