T09 · Insecure Skill Coding Practices
- Location
scripts/wp-cli.js:55- Finding
WordPress credentials may be transmitted over plaintext HTTP
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
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.
scripts/wp-cli.js:55WordPress credentials may be transmitted over plaintext HTTP
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).
- Get: `GET /posts/{id}`
- Create: `POST /posts`
- Update: `POST /posts/{id}`
- Delete: `DELETE /posts/{id}`
Common fields:
- `title`, `content`, `excerpt`
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).
- Get: `GET /pages/{id}`
- Create: `POST /pages`
- Update: `POST /pages/{id}`
- Delete: `DELETE /pages/{id}`
### Categories
- List: `GET /categories`
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.
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.
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.
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.
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.