skills.rest
uphiago
uphiagoCOMMUNITY
Explore all skills by this author →
Website𝕏@uphiagoGitHub

wordpress-full-compromise

Select and execute optimal exploitation chains for reconnoitered WordPress targets.

1.1k|191|Updated Jun 24, 2026
Search Tags:#penetration testing#wordpress#rce#account takeover#kill chain#xmlrpc#plugin cve
One-click install
npx skills add https://github.com/uphiago/recon-skills --skill wordpress-full-compromise
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wordpress-full-compromise
Source: https://github.com/uphiago/recon-skills/tree/main/chains/wordpress-full-compromise
Command: npx skills add https://github.com/uphiago/recon-skills --skill wordpress-full-compromise

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the guesswork in selecting the right exploitation path for a fully reconnoitered high-value WordPress target, ensuring penetration testers can quickly choose the highest-impact, lowest-difficulty attack chain to achieve verifiable proof of compromise for client reporting.

Core Features & Use Cases

  • 7 Pre-Vetted Kill Chains: Covers the most common WordPress vulnerability profiles including PHPInfo-based file upload, XMLRPC abuse, CORS phishing, unauthenticated plugin CVEs, brute force credential escalation, exposed MySQL databases, and staging site takeover.
  • Field-Verified Procedures: Includes real-world tested steps, edge case handling for subscriber role restrictions, and validation checks to avoid wasted effort on blocked attack paths.
  • Bundled Reference Materials: Includes guides for Mailinator-based password reset workflows and subscriber escalation pitfalls to handle complex target configurations like subdirectory WordPress installs.
  • Use Case: A penetration tester who has completed full recon on a WordPress target and confirmed findings like open XMLRPC, CORS misconfigurations, or vulnerable plugins can use this Skill to automatically select the optimal chain, execute it step-by-step, and verify success for reporting.

Quick Start

Use the wordpress-full-compromise skill to select and execute the optimal exploitation chain for your fully reconnoitered WordPress target to achieve remote code execution, account takeover, or data exfiltration.

Frequently Asked Questions about wordpress-full-compromise

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

FAQPage Schema
How do I build a WordPress kill chain for RCE after finding multiple vulnerabilities?▼

Select the optimal WordPress kill chain by applying decision matrices to confirmed vulnerabilities like XMLRPC abuse and plugin CVEs, executing step-by-step procedures to achieve remote code execution on fully reconnoitered targets.

What is the best way to achieve WordPress account takeover using CORS misconfigurations?▼

The best way to achieve WordPress account takeover via CORS misconfigurations is chaining them with field-verified kill chain procedures that exploit access control weaknesses to gain administrative privileges during authorized penetration testing.

Can I exploit an exposed MySQL database to take over a WordPress staging site?▼

You can exploit exposed MySQL databases and staging site misconfigurations using specific WordPress kill chains to extract credentials and achieve full site compromise, providing verifiable proof for penetration testing reports.

How do I handle subscriber role escalation during a WordPress penetration test?▼

Handle WordPress subscriber role escalation by referencing bundled guides detailing edge case procedures and validation checks to bypass restrictions and achieve account takeover on complex target configurations like subdirectory installs.

Does the WordPress kill chain approach work for subdirectory installs and Mailinator password resets?▼

The WordPress kill chain approach works for subdirectory installs and Mailinator password resets by utilizing bundled reference materials that provide specific workflows for handling these complex target configurations during exploitation.

When should I avoid brute force credential escalation on a WordPress target?▼

Avoid WordPress brute force credential escalation when validation checks indicate blocked attack paths, and instead select alternative pre-vetted kill chains like unauthenticated plugin CVEs or PHPInfo-based file uploads to achieve compromise.

Related Skills

Explore More Software Engineering Skills→
uphiagouphiago
1.1k

wp-plugin-automation

Automates WordPress vulnerability auditing by extracting plugin versions and matching CVEs from batches of target domains.

Community
Intermediate
enderphan94enderphan94
1

exploit-scan

Convert verified security vulnerabilities into executable proof-of-concept code and attack narratives.

Community
Advanced
cxnaivecxnaive

web-pentest

Perform authorized web application penetration testing with reconnaissance, vulnerability analysis, and proof-based exploitation.

Community
Advanced
EntroVyxEntroVyx
3

wordpress-cors-xmlrpc-rce-chain

Identify and exploit WordPress CORS, XMLRPC, and registration chains.

Community
Advanced