wordpress-full-compromise

1# WordPress Compromise Path Analysis
2 
3Use this skill to determine whether verified WordPress primitives actually
4compose into administrative control or benign code-execution proof. It is a
5chain gate, not a checklist for forcing escalation after a prerequisite fails.
6 
7## When to Use
8 
9- A plugin vulnerability has exact version and route evidence.
10- An approved identity may have an unexpected WordPress capability.
11- An upload or configuration write could reach executable handling.
12- CORS, XML-RPC, staging, or source exposure may supply a missing prerequisite.
13 
14## Prerequisites
15 
16- Explicit authorization for registration, authentication, upload, write, and
17  execution testing.
18- An approved synthetic account and disposable content.
19- Exact WordPress, plugin, theme, and hosting behavior.
20- A benign marker for any execution test.
21- Cleanup and stop conditions.
22 
23## How to Run
24 
25Build a prerequisite table:
26 
27```text
28Step                         State       Required evidence
29Component vulnerability      observed    exact version and affected operation
30Authorized identity          confirmed   approved account and current role
31Write or upload capability   unverified  synthetic artifact accepted
32Executable handling          unverified  benign marker executed
33Administrative control       not tested  approved admin-only action
34Cleanup                      planned     artifact and account removal
35```
36 
37Do not proceed past an unverified prerequisite.
38 
39## Procedure
40 
41### 1. Confirm the Component
42…