vamp-wp2shell-audit 1.0__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (13) hide show
  1. vamp_wp2shell_audit-1.0/LICENSE +21 -0
  2. vamp_wp2shell_audit-1.0/PKG-INFO +161 -0
  3. vamp_wp2shell_audit-1.0/README.md +138 -0
  4. vamp_wp2shell_audit-1.0/pyproject.toml +37 -0
  5. vamp_wp2shell_audit-1.0/setup.cfg +4 -0
  6. vamp_wp2shell_audit-1.0/vamp_wp2shell_audit.egg-info/PKG-INFO +161 -0
  7. vamp_wp2shell_audit-1.0/vamp_wp2shell_audit.egg-info/SOURCES.txt +11 -0
  8. vamp_wp2shell_audit-1.0/vamp_wp2shell_audit.egg-info/dependency_links.txt +1 -0
  9. vamp_wp2shell_audit-1.0/vamp_wp2shell_audit.egg-info/entry_points.txt +2 -0
  10. vamp_wp2shell_audit-1.0/vamp_wp2shell_audit.egg-info/requires.txt +2 -0
  11. vamp_wp2shell_audit-1.0/vamp_wp2shell_audit.egg-info/top_level.txt +2 -0
  12. vamp_wp2shell_audit-1.0/vamp_wp2shell_audit.py +2237 -0
  13. vamp_wp2shell_audit-1.0/vampsec_report.py +959 -0
vamp_wp2shell_audit-1.0/LICENSE ADDED
@@ -0,0 +1,21 @@
1
+ MIT License
2
+
3
+ Copyright (c) 2026 VampSecure Studios
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.
vamp_wp2shell_audit-1.0/PKG-INFO ADDED
@@ -0,0 +1,161 @@
1
+ Metadata-Version: 2.4
2
+ Name: vamp-wp2shell-audit
3
+ Version: 1.0
4
+ Summary: WordPress upload-vector and webshell auditor for authorized assessments
5
+ Author-email: VampSecure Studios <contact@vampsecurestudios.com>
6
+ License: MIT
7
+ Project-URL: Homepage, https://github.com/Vampsecure-Labs/vamp-wp2shell-audit
8
+ Project-URL: Repository, https://github.com/Vampsecure-Labs/vamp-wp2shell-audit
9
+ Keywords: security,pentest,audit,cybersecurity,vampsecure,wordpress,webshell,cms,web-security
10
+ Classifier: Development Status :: 5 - Production/Stable
11
+ Classifier: Environment :: Console
12
+ Classifier: Intended Audience :: Information Technology
13
+ Classifier: License :: OSI Approved :: MIT License
14
+ Classifier: Operating System :: OS Independent
15
+ Classifier: Programming Language :: Python :: 3
16
+ Classifier: Topic :: Security
17
+ Requires-Python: >=3.9
18
+ Description-Content-Type: text/markdown
19
+ License-File: LICENSE
20
+ Requires-Dist: aiohttp>=3.9.0
21
+ Requires-Dist: rich>=13.7.0
22
+ Dynamic: license-file
23
+
24
+ <h1 align="center">vamp-wp2shell-audit</h1>
25
+
26
+ <p align="center">
27
+ <img src="https://img.shields.io/badge/python-3.9%2B-blue?logo=python&logoColor=white" alt="Python 3.9+"/>
28
+ <img src="https://img.shields.io/badge/platform-linux%20%7C%20macOS%20%7C%20windows-lightgrey" alt="Platform"/>
29
+ <img src="https://img.shields.io/badge/license-MIT-green" alt="License MIT"/>
30
+ <img src="https://img.shields.io/badge/VampSecure-Labs-magenta" alt="VampSecure Labs"/>
31
+ </p>
32
+
33
+ ## Overview
34
+
35
+ `vamp-wp2shell-audit` is an async, multi-target WordPress security auditor focused on upload vectors, vulnerable plugin detection, and attack surface enumeration. It fingerprints installed plugins and themes against a curated CVE database (CVSS 7.0–9.8), probes for XML-RPC, REST API user enumeration, open upload directories, and active SQLi parameters. An optional canary upload phase — using a PHP-inert file with auto-deletion — confirms whether file-write exploitation is achievable on a live target. Also supports Joomla (CVE-2023-23752) and Drupal (CVE-2018-7600 Drupalgeddon 2) fingerprinting.
36
+
37
+ ## Features
38
+
39
+ - Async concurrent scanning with configurable semaphore (`-c/--concurrency`, default 5)
40
+ - Plugin CVE database: 10 plugins including wp-file-manager (CVE-2020-25213, CVSS 9.8), WooCommerce Payments (CVE-2023-28121), Essential Addons for Elementor (CVE-2023-32243), and more
41
+ - Theme CVE coverage and version fingerprinting via `readme.txt` / `style.css` Stable tag
42
+ - Attack surface checks: XML-RPC, REST API user enumeration, uploads directory listing, `WP_DEBUG` active
43
+ - Basic SQLi vector probing on public URL parameters
44
+ - Multi-CMS detection: WordPress, Joomla, Drupal with version fingerprinting
45
+ - Canary upload test: PHP-inert file (no syscalls, `die()` guard), auto-deleted via REST API DELETE
46
+ - Scope file enforcement — targets outside scope are skipped (`-s/--scope`)
47
+ - Risk scoring formula: composite CVSS × version-confidence factor + surface bonuses (XML-RPC +0.5, canary confirmed +3.0)
48
+ - Export to JSON, HTML (dark-theme), and unified VampSecure Labs client report (HTML + PDF)
49
+
50
+ ## Requirements
51
+
52
+ - Python 3.9 or later
53
+ - `aiohttp >= 3.9.0`
54
+ - `rich >= 13.7.0`
55
+ - Optional: `fpdf2 >= 2.7` for `--report-pdf`
56
+
57
+ ## Installation
58
+
59
+ ```bash
60
+ git clone https://github.com/belky-me/vamp-wp2shell-audit.git
61
+ cd vamp-wp2shell-audit
62
+ python3 -m venv .venv
63
+ source .venv/bin/activate # Windows: .venv\Scripts\activate
64
+ pip install -r requirements.txt
65
+ ```
66
+
67
+ ## Usage
68
+
69
+ ```
70
+ python3 vamp_wp2shell_audit.py --help
71
+ ```
72
+
73
+ ```
74
+ usage: vamp_wp2shell_audit.py [-h] [-t URL [URL ...]] [-i FICHERO] [-s FICHERO]
75
+ [-c CONCURRENCY] [--timeout TIMEOUT]
76
+ [--canary] [--force]
77
+ [-o FICHERO] [--html FICHERO] [-v]
78
+ [--client CLIENT] [--engagement ENGAGEMENT]
79
+ [--auditor AUDITOR] [--report-scope SCOPE]
80
+ [--report-html FILE] [--report-pdf FILE]
81
+
82
+ vamp-wp2shell-audit — WordPress Upload Vector Auditor (VampSecure Labs)
83
+ ```
84
+
85
+ ## Examples
86
+
87
+ ```bash
88
+ # Audit a single WordPress site
89
+ python3 vamp_wp2shell_audit.py -t https://example.com
90
+
91
+ # Audit multiple targets from file
92
+ python3 vamp_wp2shell_audit.py -i targets.txt
93
+
94
+ # Audit with scope restriction and canary upload test
95
+ python3 vamp_wp2shell_audit.py -t https://example.com -s scope.txt --canary
96
+
97
+ # Concurrent batch scan with JSON and HTML output
98
+ python3 vamp_wp2shell_audit.py -i targets.txt -c 10 -o results.json --html report.html
99
+
100
+ # Force audit even if WordPress is not detected
101
+ python3 vamp_wp2shell_audit.py -t https://example.com --force
102
+
103
+ # Generate client-ready engagement report (HTML + PDF)
104
+ python3 vamp_wp2shell_audit.py -t https://example.com \
105
+ --client "Acme Corp" --engagement "WordPress Security Review Q3 2026" \
106
+ --auditor "J. Smith" --report-html client_report.html --report-pdf client_report.pdf
107
+ ```
108
+
109
+ ## CLI Reference
110
+
111
+ | Flag | Default | Description |
112
+ |------|---------|-------------|
113
+ | `-t / --target URL [URL ...]` | — | One or more target WordPress URLs |
114
+ | `-i / --input FILE` | — | Text file with one URL per line |
115
+ | `-s / --scope FILE` | — | Scope file — targets outside scope are skipped |
116
+ | `-c / --concurrency N` | 5 | Maximum concurrent scans |
117
+ | `--timeout N` | 10 | Per-request timeout in seconds |
118
+ | `--canary` | off | Enable canary upload test on confirmed endpoints |
119
+ | `--force` | off | Audit even if WordPress is not detected |
120
+ | `-o / --output FILE` | — | Save results to JSON |
121
+ | `--html FILE` | — | Save dark-theme HTML report |
122
+ | `-v / --verbose` | off | Verbose output |
123
+ | `--client TEXT` | — | Client name for VSL engagement report |
124
+ | `--engagement TEXT` | — | Engagement title for VSL engagement report |
125
+ | `--auditor TEXT` | — | Auditor name for VSL engagement report |
126
+ | `--report-scope TEXT` | — | Scope description for VSL engagement report |
127
+ | `--report-html FILE` | — | Export unified VSL client report (HTML) |
128
+ | `--report-pdf FILE` | — | Export unified VSL client report (PDF, requires fpdf2) |
129
+
130
+ ## Output Formats
131
+
132
+ | Format | Flag | Description |
133
+ |--------|------|-------------|
134
+ | Console | (default) | Rich-colored table + per-target finding panels |
135
+ | JSON | `-o / --output FILE` | Machine-readable full result set |
136
+ | HTML | `--html FILE` | Dark-theme standalone report with finding cards |
137
+ | Client HTML | `--report-html FILE` | Unified VampSecure Labs engagement report |
138
+ | Client PDF | `--report-pdf FILE` | PDF version of the VSL client report |
139
+
140
+ ## Exit Codes
141
+
142
+ | Code | Meaning | CI/CD Behavior |
143
+ |------|---------|----------------|
144
+ | `0` | No critical or high findings | Pipeline passes |
145
+ | `1` | High-severity findings detected | Pipeline fails — review required |
146
+ | `2` | Critical-severity findings detected | Pipeline fails — immediate action required |
147
+
148
+ ## Legal Notice
149
+
150
+ Use exclusively on systems you own or for which you hold explicit written authorization from the system owner. The `--canary` flag performs a real write operation against the target server. VampSecure Studios assumes no liability for unauthorized use.
151
+
152
+ ## Part of VampSecure Labs Toolkit
153
+
154
+ `vamp-wp2shell-audit` is one tool in the VampSecure Labs security research toolkit. For the full toolkit including the orchestrator that runs all tools in sequence and aggregates findings into a single engagement report, see:
155
+
156
+ - Portfolio: [github.com/belky-me](https://github.com/belky-me)
157
+ - Orchestrator: [github.com/belky-me/vamp-orchestrator](https://github.com/belky-me/vamp-orchestrator)
158
+
159
+ ---
160
+
161
+ © VampSecure Studios — VampSecure Labs Security Research Division
vamp_wp2shell_audit-1.0/README.md ADDED
@@ -0,0 +1,138 @@
1
+ <h1 align="center">vamp-wp2shell-audit</h1>
2
+
3
+ <p align="center">
4
+ <img src="https://img.shields.io/badge/python-3.9%2B-blue?logo=python&logoColor=white" alt="Python 3.9+"/>
5
+ <img src="https://img.shields.io/badge/platform-linux%20%7C%20macOS%20%7C%20windows-lightgrey" alt="Platform"/>
6
+ <img src="https://img.shields.io/badge/license-MIT-green" alt="License MIT"/>
7
+ <img src="https://img.shields.io/badge/VampSecure-Labs-magenta" alt="VampSecure Labs"/>
8
+ </p>
9
+
10
+ ## Overview
11
+
12
+ `vamp-wp2shell-audit` is an async, multi-target WordPress security auditor focused on upload vectors, vulnerable plugin detection, and attack surface enumeration. It fingerprints installed plugins and themes against a curated CVE database (CVSS 7.0–9.8), probes for XML-RPC, REST API user enumeration, open upload directories, and active SQLi parameters. An optional canary upload phase — using a PHP-inert file with auto-deletion — confirms whether file-write exploitation is achievable on a live target. Also supports Joomla (CVE-2023-23752) and Drupal (CVE-2018-7600 Drupalgeddon 2) fingerprinting.
13
+
14
+ ## Features
15
+
16
+ - Async concurrent scanning with configurable semaphore (`-c/--concurrency`, default 5)
17
+ - Plugin CVE database: 10 plugins including wp-file-manager (CVE-2020-25213, CVSS 9.8), WooCommerce Payments (CVE-2023-28121), Essential Addons for Elementor (CVE-2023-32243), and more
18
+ - Theme CVE coverage and version fingerprinting via `readme.txt` / `style.css` Stable tag
19
+ - Attack surface checks: XML-RPC, REST API user enumeration, uploads directory listing, `WP_DEBUG` active
20
+ - Basic SQLi vector probing on public URL parameters
21
+ - Multi-CMS detection: WordPress, Joomla, Drupal with version fingerprinting
22
+ - Canary upload test: PHP-inert file (no syscalls, `die()` guard), auto-deleted via REST API DELETE
23
+ - Scope file enforcement — targets outside scope are skipped (`-s/--scope`)
24
+ - Risk scoring formula: composite CVSS × version-confidence factor + surface bonuses (XML-RPC +0.5, canary confirmed +3.0)
25
+ - Export to JSON, HTML (dark-theme), and unified VampSecure Labs client report (HTML + PDF)
26
+
27
+ ## Requirements
28
+
29
+ - Python 3.9 or later
30
+ - `aiohttp >= 3.9.0`
31
+ - `rich >= 13.7.0`
32
+ - Optional: `fpdf2 >= 2.7` for `--report-pdf`
33
+
34
+ ## Installation
35
+
36
+ ```bash
37
+ git clone https://github.com/belky-me/vamp-wp2shell-audit.git
38
+ cd vamp-wp2shell-audit
39
+ python3 -m venv .venv
40
+ source .venv/bin/activate # Windows: .venv\Scripts\activate
41
+ pip install -r requirements.txt
42
+ ```
43
+
44
+ ## Usage
45
+
46
+ ```
47
+ python3 vamp_wp2shell_audit.py --help
48
+ ```
49
+
50
+ ```
51
+ usage: vamp_wp2shell_audit.py [-h] [-t URL [URL ...]] [-i FICHERO] [-s FICHERO]
52
+ [-c CONCURRENCY] [--timeout TIMEOUT]
53
+ [--canary] [--force]
54
+ [-o FICHERO] [--html FICHERO] [-v]
55
+ [--client CLIENT] [--engagement ENGAGEMENT]
56
+ [--auditor AUDITOR] [--report-scope SCOPE]
57
+ [--report-html FILE] [--report-pdf FILE]
58
+
59
+ vamp-wp2shell-audit — WordPress Upload Vector Auditor (VampSecure Labs)
60
+ ```
61
+
62
+ ## Examples
63
+
64
+ ```bash
65
+ # Audit a single WordPress site
66
+ python3 vamp_wp2shell_audit.py -t https://example.com
67
+
68
+ # Audit multiple targets from file
69
+ python3 vamp_wp2shell_audit.py -i targets.txt
70
+
71
+ # Audit with scope restriction and canary upload test
72
+ python3 vamp_wp2shell_audit.py -t https://example.com -s scope.txt --canary
73
+
74
+ # Concurrent batch scan with JSON and HTML output
75
+ python3 vamp_wp2shell_audit.py -i targets.txt -c 10 -o results.json --html report.html
76
+
77
+ # Force audit even if WordPress is not detected
78
+ python3 vamp_wp2shell_audit.py -t https://example.com --force
79
+
80
+ # Generate client-ready engagement report (HTML + PDF)
81
+ python3 vamp_wp2shell_audit.py -t https://example.com \
82
+ --client "Acme Corp" --engagement "WordPress Security Review Q3 2026" \
83
+ --auditor "J. Smith" --report-html client_report.html --report-pdf client_report.pdf
84
+ ```
85
+
86
+ ## CLI Reference
87
+
88
+ | Flag | Default | Description |
89
+ |------|---------|-------------|
90
+ | `-t / --target URL [URL ...]` | — | One or more target WordPress URLs |
91
+ | `-i / --input FILE` | — | Text file with one URL per line |
92
+ | `-s / --scope FILE` | — | Scope file — targets outside scope are skipped |
93
+ | `-c / --concurrency N` | 5 | Maximum concurrent scans |
94
+ | `--timeout N` | 10 | Per-request timeout in seconds |
95
+ | `--canary` | off | Enable canary upload test on confirmed endpoints |
96
+ | `--force` | off | Audit even if WordPress is not detected |
97
+ | `-o / --output FILE` | — | Save results to JSON |
98
+ | `--html FILE` | — | Save dark-theme HTML report |
99
+ | `-v / --verbose` | off | Verbose output |
100
+ | `--client TEXT` | — | Client name for VSL engagement report |
101
+ | `--engagement TEXT` | — | Engagement title for VSL engagement report |
102
+ | `--auditor TEXT` | — | Auditor name for VSL engagement report |
103
+ | `--report-scope TEXT` | — | Scope description for VSL engagement report |
104
+ | `--report-html FILE` | — | Export unified VSL client report (HTML) |
105
+ | `--report-pdf FILE` | — | Export unified VSL client report (PDF, requires fpdf2) |
106
+
107
+ ## Output Formats
108
+
109
+ | Format | Flag | Description |
110
+ |--------|------|-------------|
111
+ | Console | (default) | Rich-colored table + per-target finding panels |
112
+ | JSON | `-o / --output FILE` | Machine-readable full result set |
113
+ | HTML | `--html FILE` | Dark-theme standalone report with finding cards |
114
+ | Client HTML | `--report-html FILE` | Unified VampSecure Labs engagement report |
115
+ | Client PDF | `--report-pdf FILE` | PDF version of the VSL client report |
116
+
117
+ ## Exit Codes
118
+
119
+ | Code | Meaning | CI/CD Behavior |
120
+ |------|---------|----------------|
121
+ | `0` | No critical or high findings | Pipeline passes |
122
+ | `1` | High-severity findings detected | Pipeline fails — review required |
123
+ | `2` | Critical-severity findings detected | Pipeline fails — immediate action required |
124
+
125
+ ## Legal Notice
126
+
127
+ Use exclusively on systems you own or for which you hold explicit written authorization from the system owner. The `--canary` flag performs a real write operation against the target server. VampSecure Studios assumes no liability for unauthorized use.
128
+
129
+ ## Part of VampSecure Labs Toolkit
130
+
131
+ `vamp-wp2shell-audit` is one tool in the VampSecure Labs security research toolkit. For the full toolkit including the orchestrator that runs all tools in sequence and aggregates findings into a single engagement report, see:
132
+
133
+ - Portfolio: [github.com/belky-me](https://github.com/belky-me)
134
+ - Orchestrator: [github.com/belky-me/vamp-orchestrator](https://github.com/belky-me/vamp-orchestrator)
135
+
136
+ ---
137
+
138
+ © VampSecure Studios — VampSecure Labs Security Research Division
vamp_wp2shell_audit-1.0/pyproject.toml ADDED
@@ -0,0 +1,37 @@
1
+ [build-system]
2
+ requires = ["setuptools>=68", "wheel"]
3
+ build-backend = "setuptools.build_meta"
4
+
5
+ [project]
6
+ name = "vamp-wp2shell-audit"
7
+ version = "1.0"
8
+ description = "WordPress upload-vector and webshell auditor for authorized assessments"
9
+ readme = "README.md"
10
+ license = { text = "MIT" }
11
+ requires-python = ">=3.9"
12
+ authors = [{ name = "VampSecure Studios", email = "contact@vampsecurestudios.com" }]
13
+ keywords = ["security", "pentest", "audit", "cybersecurity", "vampsecure", "wordpress", "webshell", "cms", "web-security"]
14
+ classifiers = [
15
+ "Development Status :: 5 - Production/Stable",
16
+ "Environment :: Console",
17
+ "Intended Audience :: Information Technology",
18
+ "License :: OSI Approved :: MIT License",
19
+ "Operating System :: OS Independent",
20
+ "Programming Language :: Python :: 3",
21
+ "Topic :: Security",
22
+ ]
23
+ dependencies = [
24
+ "aiohttp>=3.9.0",
25
+ "rich>=13.7.0",
26
+ ]
27
+
28
+
29
+ [project.scripts]
30
+ vamp-wp2shell-audit = "vamp_wp2shell_audit:main"
31
+
32
+ [project.urls]
33
+ Homepage = "https://github.com/Vampsecure-Labs/vamp-wp2shell-audit"
34
+ Repository = "https://github.com/Vampsecure-Labs/vamp-wp2shell-audit"
35
+
36
+ [tool.setuptools]
37
+ py-modules = ["vamp_wp2shell_audit", "vampsec_report"]
vamp_wp2shell_audit-1.0/setup.cfg ADDED
@@ -0,0 +1,4 @@
1
+ [egg_info]
2
+ tag_build =
3
+ tag_date = 0
4
+
vamp_wp2shell_audit-1.0/vamp_wp2shell_audit.egg-info/PKG-INFO ADDED
@@ -0,0 +1,161 @@
1
+ Metadata-Version: 2.4
2
+ Name: vamp-wp2shell-audit
3
+ Version: 1.0
4
+ Summary: WordPress upload-vector and webshell auditor for authorized assessments
5
+ Author-email: VampSecure Studios <contact@vampsecurestudios.com>
6
+ License: MIT
7
+ Project-URL: Homepage, https://github.com/Vampsecure-Labs/vamp-wp2shell-audit
8
+ Project-URL: Repository, https://github.com/Vampsecure-Labs/vamp-wp2shell-audit
9
+ Keywords: security,pentest,audit,cybersecurity,vampsecure,wordpress,webshell,cms,web-security
10
+ Classifier: Development Status :: 5 - Production/Stable
11
+ Classifier: Environment :: Console
12
+ Classifier: Intended Audience :: Information Technology
13
+ Classifier: License :: OSI Approved :: MIT License
14
+ Classifier: Operating System :: OS Independent
15
+ Classifier: Programming Language :: Python :: 3
16
+ Classifier: Topic :: Security
17
+ Requires-Python: >=3.9
18
+ Description-Content-Type: text/markdown
19
+ License-File: LICENSE
20
+ Requires-Dist: aiohttp>=3.9.0
21
+ Requires-Dist: rich>=13.7.0
22
+ Dynamic: license-file
23
+
24
+ <h1 align="center">vamp-wp2shell-audit</h1>
25
+
26
+ <p align="center">
27
+ <img src="https://img.shields.io/badge/python-3.9%2B-blue?logo=python&logoColor=white" alt="Python 3.9+"/>
28
+ <img src="https://img.shields.io/badge/platform-linux%20%7C%20macOS%20%7C%20windows-lightgrey" alt="Platform"/>
29
+ <img src="https://img.shields.io/badge/license-MIT-green" alt="License MIT"/>
30
+ <img src="https://img.shields.io/badge/VampSecure-Labs-magenta" alt="VampSecure Labs"/>
31
+ </p>
32
+
33
+ ## Overview
34
+
35
+ `vamp-wp2shell-audit` is an async, multi-target WordPress security auditor focused on upload vectors, vulnerable plugin detection, and attack surface enumeration. It fingerprints installed plugins and themes against a curated CVE database (CVSS 7.0–9.8), probes for XML-RPC, REST API user enumeration, open upload directories, and active SQLi parameters. An optional canary upload phase — using a PHP-inert file with auto-deletion — confirms whether file-write exploitation is achievable on a live target. Also supports Joomla (CVE-2023-23752) and Drupal (CVE-2018-7600 Drupalgeddon 2) fingerprinting.
36
+
37
+ ## Features
38
+
39
+ - Async concurrent scanning with configurable semaphore (`-c/--concurrency`, default 5)
40
+ - Plugin CVE database: 10 plugins including wp-file-manager (CVE-2020-25213, CVSS 9.8), WooCommerce Payments (CVE-2023-28121), Essential Addons for Elementor (CVE-2023-32243), and more
41
+ - Theme CVE coverage and version fingerprinting via `readme.txt` / `style.css` Stable tag
42
+ - Attack surface checks: XML-RPC, REST API user enumeration, uploads directory listing, `WP_DEBUG` active
43
+ - Basic SQLi vector probing on public URL parameters
44
+ - Multi-CMS detection: WordPress, Joomla, Drupal with version fingerprinting
45
+ - Canary upload test: PHP-inert file (no syscalls, `die()` guard), auto-deleted via REST API DELETE
46
+ - Scope file enforcement — targets outside scope are skipped (`-s/--scope`)
47
+ - Risk scoring formula: composite CVSS × version-confidence factor + surface bonuses (XML-RPC +0.5, canary confirmed +3.0)
48
+ - Export to JSON, HTML (dark-theme), and unified VampSecure Labs client report (HTML + PDF)
49
+
50
+ ## Requirements
51
+
52
+ - Python 3.9 or later
53
+ - `aiohttp >= 3.9.0`
54
+ - `rich >= 13.7.0`
55
+ - Optional: `fpdf2 >= 2.7` for `--report-pdf`
56
+
57
+ ## Installation
58
+
59
+ ```bash
60
+ git clone https://github.com/belky-me/vamp-wp2shell-audit.git
61
+ cd vamp-wp2shell-audit
62
+ python3 -m venv .venv
63
+ source .venv/bin/activate # Windows: .venv\Scripts\activate
64
+ pip install -r requirements.txt
65
+ ```
66
+
67
+ ## Usage
68
+
69
+ ```
70
+ python3 vamp_wp2shell_audit.py --help
71
+ ```
72
+
73
+ ```
74
+ usage: vamp_wp2shell_audit.py [-h] [-t URL [URL ...]] [-i FICHERO] [-s FICHERO]
75
+ [-c CONCURRENCY] [--timeout TIMEOUT]
76
+ [--canary] [--force]
77
+ [-o FICHERO] [--html FICHERO] [-v]
78
+ [--client CLIENT] [--engagement ENGAGEMENT]
79
+ [--auditor AUDITOR] [--report-scope SCOPE]
80
+ [--report-html FILE] [--report-pdf FILE]
81
+
82
+ vamp-wp2shell-audit — WordPress Upload Vector Auditor (VampSecure Labs)
83
+ ```
84
+
85
+ ## Examples
86
+
87
+ ```bash
88
+ # Audit a single WordPress site
89
+ python3 vamp_wp2shell_audit.py -t https://example.com
90
+
91
+ # Audit multiple targets from file
92
+ python3 vamp_wp2shell_audit.py -i targets.txt
93
+
94
+ # Audit with scope restriction and canary upload test
95
+ python3 vamp_wp2shell_audit.py -t https://example.com -s scope.txt --canary
96
+
97
+ # Concurrent batch scan with JSON and HTML output
98
+ python3 vamp_wp2shell_audit.py -i targets.txt -c 10 -o results.json --html report.html
99
+
100
+ # Force audit even if WordPress is not detected
101
+ python3 vamp_wp2shell_audit.py -t https://example.com --force
102
+
103
+ # Generate client-ready engagement report (HTML + PDF)
104
+ python3 vamp_wp2shell_audit.py -t https://example.com \
105
+ --client "Acme Corp" --engagement "WordPress Security Review Q3 2026" \
106
+ --auditor "J. Smith" --report-html client_report.html --report-pdf client_report.pdf
107
+ ```
108
+
109
+ ## CLI Reference
110
+
111
+ | Flag | Default | Description |
112
+ |------|---------|-------------|
113
+ | `-t / --target URL [URL ...]` | — | One or more target WordPress URLs |
114
+ | `-i / --input FILE` | — | Text file with one URL per line |
115
+ | `-s / --scope FILE` | — | Scope file — targets outside scope are skipped |
116
+ | `-c / --concurrency N` | 5 | Maximum concurrent scans |
117
+ | `--timeout N` | 10 | Per-request timeout in seconds |
118
+ | `--canary` | off | Enable canary upload test on confirmed endpoints |
119
+ | `--force` | off | Audit even if WordPress is not detected |
120
+ | `-o / --output FILE` | — | Save results to JSON |
121
+ | `--html FILE` | — | Save dark-theme HTML report |
122
+ | `-v / --verbose` | off | Verbose output |
123
+ | `--client TEXT` | — | Client name for VSL engagement report |
124
+ | `--engagement TEXT` | — | Engagement title for VSL engagement report |
125
+ | `--auditor TEXT` | — | Auditor name for VSL engagement report |
126
+ | `--report-scope TEXT` | — | Scope description for VSL engagement report |
127
+ | `--report-html FILE` | — | Export unified VSL client report (HTML) |
128
+ | `--report-pdf FILE` | — | Export unified VSL client report (PDF, requires fpdf2) |
129
+
130
+ ## Output Formats
131
+
132
+ | Format | Flag | Description |
133
+ |--------|------|-------------|
134
+ | Console | (default) | Rich-colored table + per-target finding panels |
135
+ | JSON | `-o / --output FILE` | Machine-readable full result set |
136
+ | HTML | `--html FILE` | Dark-theme standalone report with finding cards |
137
+ | Client HTML | `--report-html FILE` | Unified VampSecure Labs engagement report |
138
+ | Client PDF | `--report-pdf FILE` | PDF version of the VSL client report |
139
+
140
+ ## Exit Codes
141
+
142
+ | Code | Meaning | CI/CD Behavior |
143
+ |------|---------|----------------|
144
+ | `0` | No critical or high findings | Pipeline passes |
145
+ | `1` | High-severity findings detected | Pipeline fails — review required |
146
+ | `2` | Critical-severity findings detected | Pipeline fails — immediate action required |
147
+
148
+ ## Legal Notice
149
+
150
+ Use exclusively on systems you own or for which you hold explicit written authorization from the system owner. The `--canary` flag performs a real write operation against the target server. VampSecure Studios assumes no liability for unauthorized use.
151
+
152
+ ## Part of VampSecure Labs Toolkit
153
+
154
+ `vamp-wp2shell-audit` is one tool in the VampSecure Labs security research toolkit. For the full toolkit including the orchestrator that runs all tools in sequence and aggregates findings into a single engagement report, see:
155
+
156
+ - Portfolio: [github.com/belky-me](https://github.com/belky-me)
157
+ - Orchestrator: [github.com/belky-me/vamp-orchestrator](https://github.com/belky-me/vamp-orchestrator)
158
+
159
+ ---
160
+
161
+ © VampSecure Studios — VampSecure Labs Security Research Division
vamp_wp2shell_audit-1.0/vamp_wp2shell_audit.egg-info/SOURCES.txt ADDED
@@ -0,0 +1,11 @@
1
+ LICENSE
2
+ README.md
3
+ pyproject.toml
4
+ vamp_wp2shell_audit.py
5
+ vampsec_report.py
6
+ vamp_wp2shell_audit.egg-info/PKG-INFO
7
+ vamp_wp2shell_audit.egg-info/SOURCES.txt
8
+ vamp_wp2shell_audit.egg-info/dependency_links.txt
9
+ vamp_wp2shell_audit.egg-info/entry_points.txt
10
+ vamp_wp2shell_audit.egg-info/requires.txt
11
+ vamp_wp2shell_audit.egg-info/top_level.txt
vamp_wp2shell_audit-1.0/vamp_wp2shell_audit.egg-info/entry_points.txt ADDED
@@ -0,0 +1,2 @@
1
+ [console_scripts]
2
+ vamp-wp2shell-audit = vamp_wp2shell_audit:main
vamp_wp2shell_audit-1.0/vamp_wp2shell_audit.egg-info/requires.txt ADDED
@@ -0,0 +1,2 @@
1
+ aiohttp>=3.9.0
2
+ rich>=13.7.0
vamp_wp2shell_audit-1.0/vamp_wp2shell_audit.egg-info/top_level.txt ADDED
@@ -0,0 +1,2 @@
1
+ vamp_wp2shell_audit
2
+ vampsec_report