Back to skill

Security audit

WordPress REST API CLI

Security checks for vulnerabilities and agentic risk

Overview

This WordPress CLI appears legitimate, but it needs Review because it can change or delete live site content and may send WordPress credentials over non-HTTPS if misconfigured.

Install only if you are comfortable giving this CLI WordPress API credentials that can create, edit, and delete site content. Use a dedicated low-privilege application password, configure only an HTTPS WP_BASE_URL, prefer drafts or staging first, and treat delete and raw request commands as live-site operations.

Vulnerability Patterns
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)

T09 · Insecure Skill Coding Practices

Warning
Location
scripts/wp-cli.js:55
Finding

WordPress credentials may be transmitted over plaintext HTTP

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (7)

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
80% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · assets/wordpress-rest-api-guide.md (reported line 18)May include surrounding context.

md
- Get: `GET /posts/{id}`
- Create: `POST /posts`
- Update: `POST /posts/{id}`
- Delete: `DELETE /posts/{id}`

Common fields:
- `title`, `content`, `excerpt`

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
80% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · assets/wordpress-rest-api-guide.md (reported line 31)May include surrounding context.

md
- Get: `GET /pages/{id}`
- Create: `POST /pages`
- Update: `POST /pages/{id}`
- Delete: `DELETE /pages/{id}`

### Categories
- List: `GET /categories`

Undeclared Tool Scope

Medium
Category
MCP Least Privilege
Confidence
93% confidence
Finding

The skill advertises and operationally requires access to environment variables for credentials and network access to a WordPress instance, but it does not declare any explicit tool scope such as permissions or allowed-tools. This creates an authorization gap where the runtime may grant broader capabilities than reviewers or orchestrators expect, increasing the risk of unintended outbound requests or secret access.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

This markdown file documents create, update, and delete operations for WordPress posts, including DELETE /posts/{id}, but does not warn users that these actions modify or remove live site content. For markdown files, safety-affecting behaviors that impact user data or system integrity should include a clear warning.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The guide lists write operations for pages, including deletion, but provides no caution that these requests can alter or permanently remove website pages. In markdown skill documentation, such behaviors should be disclosed because they can affect user data and site integrity.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

This code exposes posts:delete and pages:delete operations that perform irreversible remote deletions via HTTP DELETE, but there is no confirmation prompt, warning message, or explanatory comment/docstring disclosing that user content will be removed. For code files, destructive operations should have some visible disclosure unless clearly warned elsewhere, and no such warning is present in this file.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
84% confidence
Finding

The request command allows arbitrary HTTP methods, paths, and optional JSON bodies to be transmitted to the configured WordPress server, but the code provides no user-facing notice that supplied data will be sent over the network. Although network access is central to this CLI, this generic passthrough operation is broad enough that an explicit warning would help users understand that arbitrary payloads may be transmitted to the remote site.

Content

No source excerpt is available for this finding.