WordPress Penetration Testing

Fail

Audited by Snyk on Apr 15, 2026

Risk Level: CRITICAL
Full Analysis

HIGH W007: Insecure credential handling detected in skill instructions.

  • Insecure credential handling detected (high risk: 1.00). The skill contains multiple examples that embed API tokens, HTTP auth credentials, and plaintext passwords directly into commands and scripts (e.g., --api-token YOUR_API_TOKEN, --http-auth admin:password, set PASSWORD jessica), which requires the LLM to handle and output secret values verbatim and is therefore insecure.

CRITICAL E006: Malicious code pattern detected in skill scripts.

  • Malicious code pattern detected (high risk: 1.00). The content contains explicit offensive techniques and backdoor patterns—credential brute-forcing, XML-RPC multicall abuse, exploitation via Metasploit, creating/uploading PHP webshells and reverse shells, and evasion/proxy instructions—indicating high-risk malicious/abusive behavior if used without authorization.

MEDIUM W011: Third-party content exposure detected (indirect prompt injection risk).

  • Third-party content exposure detected (high risk: 1.00). This skill explicitly fetches and parses untrusted public web content as part of its core workflow (e.g., curl/wpscan calls to http://target.com/readme.html, /wp-json/wp/v2/users, /xmlrpc.php and numerous wp-content/wp-includes plugin/theme URLs) and then uses those results to drive enumeration, exploitation, and subsequent tool actions, which meets the criteria for indirect prompt-injection exposure.

Issues (3)

W007
HIGH

Insecure credential handling detected in skill instructions.

E006
CRITICAL

Malicious code pattern detected in skill scripts.

W011
MEDIUM

Third-party content exposure detected (indirect prompt injection risk).

Audit Metadata
Risk Level
CRITICAL
Analyzed
Apr 15, 2026, 06:10 PM
Issues
3
Security Audit — snyk — WordPress Penetration Testing