wordpress-penetration-testing
Assess WordPress Security
WordPress assessments require repeatable checks for versions, plugins, themes, users, and exposure. This skill organizes authorized testing steps and reporting outputs for Claude, Codex, and Claude Code users.
Do not auto-install this skill.
The canonical policy requires operator review before any installation action.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "wordpress-penetration-testing" from https://skillstore.io/skills/sickn33-wordpress-penetration-testing.md and its manifest at https://skillstore.io/api/skills/sickn33-wordpress-penetration-testing/manifest. Verify the artifact. Do not auto-install. Inspect the skill and report your findings, then wait for an operator or manual installation decision.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "wordpress-penetration-testing". Plan a WordPress assessment for a small business site with written authorization.
Expected outcome:
A phased checklist covering scope confirmation, passive discovery, WPScan enumeration, plugin and theme review, controlled validation, evidence capture, and remediation reporting.
Using "wordpress-penetration-testing". Summarize these findings: old plugin, exposed users endpoint, readable readme file.
Expected outcome:
A concise risk summary that explains exposed version and user data, affected components, likely impact, and recommended fixes.
Using "wordpress-penetration-testing". Create a report outline for a completed WordPress security review.
Expected outcome:
A professional report structure with executive summary, methodology, findings, evidence, severity, remediation, retest steps, and scope notes.
Security Audit
CriticalThe audit confirms extensive offensive WordPress testing guidance. It includes active scanning, credential attacks, Metasploit exploitation, reverse shells, webshell creation, and proxy guidance. Many Markdown syntax findings are false positives, but the confirmed findings show high-risk dual-use and abuse-enabling content.
Confirmed security concerns (12)
Show all 12 confirmed findings
Capability review items (100)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
⚡ Contains scripts (1)
⚙️ External commands (50)
🌐 Network access (50)
Detected Patterns
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-wordpress-penetration-testing/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-wordpress-penetration-testing?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-wordpress-penetration-testing?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-wordpress-penetration-testing/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-wordpress-penetration-testing.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). wordpress-penetration-testing security audit report (audit version 6) [Author version 1.1]. Skillstore. https://skillstore.io/skills/sickn33-wordpress-penetration-testing/audits/6BibTeX citation
@techreport{sickn33-sickn33-wordpress-penetration-testing-2026,
author = {sickn33},
title = {wordpress-penetration-testing security audit report (audit version 6)},
institution = {Skillstore},
year = {2026},
number = {6},
url = {https://skillstore.io/skills/sickn33-wordpress-penetration-testing/audits/6},
note = {Author version 1.1}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "wordpress-penetration-testing security audit report (audit version 6)"
version: "1.1"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/sickn33-wordpress-penetration-testing/audits/6"
identifiers:
- type: other
value: "skillstore:sickn33-wordpress-penetration-testing:audit:6"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Prepare Client Assessment
Build a scoped WordPress test plan covering discovery, enumeration, vulnerability review, and reporting evidence.
Review Site Exposure
Check visible WordPress versions, plugins, themes, users, and public endpoints before a remediation sprint.
Validate Security Training Lab
Create a controlled lab workflow that demonstrates WordPress enumeration and defense validation.
Try These Prompts
Create a WordPress security assessment checklist for an authorized target. Include scope, safe enumeration steps, evidence to collect, and reporting sections.
Review these WordPress enumeration notes and identify likely risks, missing evidence, and remediation priorities. Do not add exploitation steps.
Turn this WordPress finding list into a prioritized remediation plan with affected components, business impact, evidence, and verification steps.
Design a scoped WordPress penetration test plan for a signed engagement. Include rules of engagement, rate limits, tool choices, safety controls, and deliverables.
Best Practices
- Confirm written authorization, scope, rate limits, and testing windows before using any tool output.
- Prefer passive checks and low-impact enumeration before aggressive scans or credential testing.
- Record evidence, timestamps, target URLs, tool versions, and remediation guidance for every finding.
Avoid
- Do not test public WordPress sites without explicit written permission.
- Do not run credential attacks, exploit modules, or shell upload steps on production systems without approval.
- Do not treat automated scanner output as confirmed without manual validation and business context.
Frequently Asked Questions
Is this skill only for authorized testing?
Does it require WPScan?
Can it verify plugin vulnerabilities?
Can it help write a client report?
What risks does this skill have?
Should it be used on production sites?
Developer Details
Author
sickn33License
MIT
Author version
v1.1
Skillstore revision
r1
Version notice
The author-declared version is not valid SemVer.
Repository
https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/wordpress-penetration-testingRef
3e4b6c31a74a3bd1a291c98cf585d720cb9fbc88
Maintenance freshness
7/18/2026
Usage
8 downloads · 158 views
File structure
📄 SKILL.md