wordpress-penetration-testing

Fail

Audited by Snyk on Aug 10, 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 and passwords directly into commands/requests (e.g., "--api-token YOUR_API_TOKEN", "admin:password", "set PASSWORD jessica", and hardcoded passwords in the XML-RPC payload), which requires the LLM to handle or reproduce secret values verbatim and is therefore insecure.

CRITICAL E006: Malicious code pattern detected in skill scripts.

  • Malicious code pattern detected (high risk: 1.00). High-risk: the document contains explicit offensive instructions for credential theft, brute-force, remote code execution, webshell/backdoor installation, and data exfiltration suitable for misuse outside authorized testing.

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

  • Third-party content exposure detected (medium risk: 0.30). The runtime workflow ingests outsider-authored free text from the target’s AI Connector endpoints (e.g., POST body field prompt and other responses) via /wp-json/ai/v1/prompt and related /wp-json/ai/v1/* calls, so an outsider can submit poison/prompt text that the LLM processes.

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
Aug 10, 2026, 06:43 PM
Issues
3
Security Audit — snyk — wordpress-penetration-testing