# kh4sh3i/xmlrpc-exploit architecture

> Architecture diagram of the GitHub repository kh4sh3i/xmlrpc-exploit, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-08-29). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/kh4sh3i/xmlrpc-exploit
- Repository: https://github.com/kh4sh3i/xmlrpc-exploit

## Overview

##### Project type and purpose
- This is an open-source security/exploitation tool (no frontend/backend code) documented entirely in the README.
- Purpose: automate discovery and exploitation of WordPress xmlrpc.php endpoints using techniques like method enumeration, pingback attacks, and brute-force login attempts.

##### File structure
- Top-level contains only LICENSE and README.md → the “project” is essentially a set of documented attack recipes, not a multi-component application.
- No code directories to inspect; the README is the sole source of logic and flow.

##### README for insights
- Sections cover:
- “Dorks” (search queries to locate targets)
- XML-RPC server discovery (system.listMethods)
- Pingback-based DDoS or Cloudflare bypass
- Brute-force login via system.multicall + wp.getUsersBlogs

##### Main components and their interactions
a. Components:
1. Scanner Module (“Dorks Engine”)
2. Discovery Module (XML-RPC enumeration)
3. Exploitation Module
- Pingback attack sub-module
- Brute-force sub-module
4. Target WordPress Servers
5. (Optional) Reflection Hosts / Victim URLs for pingbacks
b. Relationships / Data Flow:
- Scanner → yields list of candidate target domains
- For each target, Discovery → sends system.listMethods → parses response
- If xmlrpc.php is enabled, Exploitation Module branches based on attack type:
– Pingback attack → constructs pingback.ping calls → routes traffic via target to reflection hosts
– Brute-force attack → constructs system.multicall payloads with credential permutations → analyzes faultCodes in responses
c. Architectural patterns / design principles
- Pipeline pattern: sequential stages (scan → enumerate → exploit).
- Plugin-style attack modules: each attack type is a separate sub-component with a uniform interface (“invoke(xmlrpc_method, params)”).
d. Key technologies
- HTTP POST over TCP to /xmlrpc.php
- XML-RPC protocol (methodCall/methodResponse)
- WordPress XML-RPC API methods (system.listMethods, pingback.ping, system.multicall, wp.getUsersBlogs)

3. Attach endpoints: “WordPress/XML-RPC Server” on the right side of each flow.

## Diagram (Mermaid)

```mermaid
flowchart TB
    %% External collateral services
    SearchEngines["Search Engines (Dorks Sources)"]:::collateral
    Reflection["Reflection Hosts / Victim URLs"]:::collateral

    %% Internal modules
    Scanner["Dorks Engine"]:::internal
    Discovery["Discovery Module\n(XML-RPC Enumeration)"]:::internal

    subgraph "Exploitation Module"
        Pingback["Pingback Sub-Module"]:::internal
        BruteForce["Brute-Force Sub-Module"]:::internal
    end

    %% External target
    WPServer["Target WordPress Servers"]:::external

    %% Data flows
    SearchEngines -->|"dorks queries"| Scanner
    Scanner -->|"candidate targets"| Discovery
    Discovery -->|"xmlrpc enabled"| Pingback
    Discovery -->|"xmlrpc enabled"| BruteForce
    Pingback -->|"POST methodCall pingback.ping"| WPServer
    Pingback -->|"redirect traffic"| Reflection
    BruteForce -->|"POST methodCall system.multicall"| WPServer

    %% Click events
    click Scanner "https://github.com/kh4sh3i/xmlrpc-exploit/blob/main/README.md"
    click Discovery "https://github.com/kh4sh3i/xmlrpc-exploit/blob/main/README.md"
    click Pingback "https://github.com/kh4sh3i/xmlrpc-exploit/blob/main/README.md"
    click BruteForce "https://github.com/kh4sh3i/xmlrpc-exploit/blob/main/README.md"
    click WPServer "https://github.com/kh4sh3i/xmlrpc-exploit/blob/main/README.md"
    click Reflection "https://github.com/kh4sh3i/xmlrpc-exploit/blob/main/README.md"

    %% Styles
    classDef internal fill:#ADD8E6,stroke:#000,stroke-width:1px
    classDef external fill:#90EE90,stroke:#000,stroke-width:1px
    classDef collateral fill:#FFA500,stroke:#000,stroke-width:1px
```
