wordpress-cors-xmlrpc-rce-chain

Chain WordPress CORS, XMLRPC, and open registration misconfigurations into remote code execution.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the manual, error-prone work of chaining multiple common WordPress misconfigurations to achieve remote code execution during penetration testing and red team engagements, reducing exploitation time from hours to minutes.

Core Features & Use Cases

  • Proven Field-Validated Chain: Combines CORS credential reflection, XMLRPC abuse, and open registration into a reliable end-to-end exploitation workflow tested across 58+ company targets in mass recon campaigns.
  • Blocker Bypass Guidance: Includes workarounds for common chain breakers like subscriber role upload restrictions, staging environment XMLRPC 405 errors, and failed IMDS SSRF attempts via pingback.ping.
  • Real-World Examples: Documents actual target case studies including ecommerce-wine.com, senior-living-platform.com, and mattress-retailer.com to illustrate chain application and edge case handling. Red teamers and penetration testers can use this skill to quickly validate and exploit chained WordPress vulnerabilities during authorized security assessments.

Quick Start

Use this skill to execute the full WordPress CORS → XMLRPC → RCE attack chain against a target WordPress instance that has CORS credential reflection, enabled XMLRPC, or open user registration enabled.

Frequently Asked Questions about wordpress-cors-xmlrpc-rce-chain

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

FAQPage Schema
How do I achieve RCE on WordPress by chaining CORS, XMLRPC, and open registration misconfigurations?

Remote code execution on WordPress is achieved by chaining CORS credential reflection, enabled XMLRPC, and open user registration to progressively escalate privileges and execute code. This chain automates exploitation from initial detection to full server control during penetration tests.

How do I bypass WordPress subscriber role upload restrictions during an XMLRPC exploitation chain?

Subscriber upload restrictions are bypassed by leveraging XMLRPC credential reflection combined with alternative endpoint interactions to upload payloads. The chain includes specific workarounds for subscriber role upload restrictions to maintain the exploitation flow.

Why does XMLRPC return a 405 error on WordPress staging environments during a penetration test?

XMLRPC 405 errors on staging environments typically indicate the endpoint is restricted or disabled by security configurations. The chain provides specific workarounds for staging environment XMLRPC 405 errors to restore the attack path.

Can I use this WordPress attack chain for mass recon campaigns across multiple targets?

This WordPress attack chain is validated for mass recon campaigns across 58+ company targets, making it suitable for large-scale penetration testing. It reliably detects and exploits chained misconfigurations during authorized security assessments.

What should I do when a WordPress pingback.ping SSRF attempt fails during an XMLRPC attack?

Failed pingback.ping SSRF attempts are addressed through documented blocker bypass guidance included in the chain. The skill provides alternative exploitation paths for IMDS SSRF attempts and other common chain breakers.