wordpress-penetration-testing — Claude Code skill: vulnerability
This skill audits WordPress installations for common vulnerabilities and REST API permission issues in plugins. Designed for authorized security assessments.
npx skills add sickn33/agentic-awesome-skills --skill wordpress-penetration-testing -a claude-codeWhat wordpress-penetration-testing does
The skill automates detection of typical WordPress misconfigurations: broken REST API access controls, outdated plugins, weak security settings. It uses WPScan, Metasploit Framework, and Burp Suite for scanning and analysis. Nmap handles initial discovery, cURL runs verification checks.
Before any scan, the skill enforces a confirmation gate: you provide the exact target URL or IP, confirm written authorization from the owner, and the skill displays the command and its effect. Without confirmation, it stays read-only and offers defensive guidance only. It accounts for real constraints: WAF may block traffic, rate limiting slows brute-force attempts, some plugins produce false results.
Agree with the owner on source IPs, request rates, maintenance windows, and stop conditions beforehand. Use throttle to reduce load—for example, --throttle 1000—and do not circumvent agreed limits by switching proxies or authentication channels.
What it helps with
- find vulnerabilities in WordPress REST API
- check plugin access control boundaries
- discover outdated or dangerous extensions
- assess site security configuration
- audit a site before going live
Example prompts for the agent
- Scan example.com for WordPress vulnerabilities
- Check REST API permissions on example.com, I have owner authorization
- Find access control issues in the WordPress installation
How to install wordpress-penetration-testing
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill wordpress-penetration-testing -a claude-code2Manually: put the files in place
~/.claude/skills/wordpress-penetration-testing/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/wordpress-penetration-testing/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill wordpress-penetration-testing -a codex2Manually: put the files in place
.agents/skills/wordpress-penetration-testing/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill wordpress-penetration-testing -a cursor2Manually: put the files in place
.cursor/skills/wordpress-penetration-testing/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install sickn33/agentic-awesome-skills wordpress-penetration-testing2Manually: put the files in place
.github/skills/wordpress-penetration-testing/SKILL.md1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill wordpress-penetration-testing -a gemini-cli2Platform CLI
gemini skills install https://github.com/sickn33/agentic-awesome-skills --path skills/wordpress-penetration-testingManually: put the files in place
.devin/skills/wordpress-penetration-testing/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill wordpress-penetration-testing -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set80
The whole set →Similar
Questions about wordpress-penetration-testing
How do I install wordpress-penetration-testing in Claude Code?
Run npx skills add sickn33/agentic-awesome-skills --skill wordpress-penetration-testing -a claude-code, then open ~/.claude/skills/wordpress-penetration-testing/SKILL.md.
What does wordpress-penetration-testing do?
It scans WordPress sites for common vulnerabilities, checks plugin REST API permissions, and identifies security misconfigurations. It requires written owner authorization before any testing.
What tools does this skill need?
WPScan, Metasploit Framework, Burp Suite or OWASP ZAP, Nmap, and cURL or wget. WPScan comes pre-installed in Kali Linux.
Source text
SKILL.md · MIT
--- name: wordpress-penetration-testing description: "Assess WordPress installations for common vulnerabilities and installed core/plugin REST permission boundaries." risk: offensive source: community author: zebbern date_added: "2026-02-27" --- > **⚠️ AUTHORIZED USE ONLY** > This skill is for educational purposes or authorized security assessments only. > You must have explicit, written permission from the system owner before using this tool. > Misuse of this tool is illegal and strictly prohibited. > **Mandatory confirmation gate** > Before running any command that probes, exploits, changes, persists on, extracts data from, or attempts credential access against a target: > 1. Ask the user to state the exact target URL, IP, account, or resource. > 2. Ask the user to confirm written authorization and the permitted scope. > 3. Show the exact command(s) and explain their expected effect. > 4. Wait for explicit confirmation in the current conversation. > > Without that confirmation, remain read-only and provide defensive guidance only. Prefer a sandbox, disposable VM, or controlled lab. > AUTHORIZED USE ONLY: Use this skill only for authorized security assessments, defensive validation, or controlled educational environments. # WordPress Penetration Testing ## Detailed Guide Read [the detailed guide](references/detailed-guide.md) before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely. ## Prerequisites ### Required Tools - WPScan (pre-installed in Kali Linux) - Metasploit Framework - Burp Suite or OWASP ZAP - Nmap for initial discovery - cURL or wget ### Required Knowledge - WordPress architecture and structure - Web application testing fundamentals - HTTP protocol understanding - Common web vulnerabilities (OWASP Top 10) ## Constraints and Limitations ### Legal Considerations - Obtain written authorization before testing - Stay within defined scope - Document all testing activities - Follow responsible disclosure ### Technical Limitations - WAF may block scanning - Rate limiting may prevent brute-force - Some plugins may have false negatives - XML-RPC may be disabled ### Assessment Traffic Controls - Agree source IPs, request rates, maintenance window, stop conditions and any proxy with the owner. - Throttle requests: `--throttle 1000` is an example to verify against installed WPScan help. - A blocked scan is a finding or scope limit; do not rotate proxies or switch authentication channels to evade agreed controls. ## When to Use This skill is applicable to execute the workflow or actions described in the overview.
© zebbern · MIT · sickn33/agentic-awesome-skills