T09 · Insecure Skill Coding Practices
- Location
SKILL.md:40- Finding
Bearer API Token May Be Exposed Through Command-Line Configuration
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a coherent WordPress admin connector, but it gives an AI agent broad site-changing authority and uses a bearer token setup pattern without enough user-facing guardrails.
Install only with a narrowly scoped WordPress Access Point, preferably on staging first. Treat the API key like a password, avoid pasting it into shared shells or logs, use IP allowlisting and audit logs, and require human approval for deletes, user changes, WooCommerce/customer/order changes, plugin settings, and Code Snippets operations.
SKILL.md:40Bearer API Token May Be Exposed Through Command-Line Configuration
The skill advertises broad WordPress administrative capabilities including create, update, delete, moderation, user management, plugin integrations, and cache flushing, but does not include any caution that these operations can cause destructive, site-wide, or irreversible changes. In a skill that enables remote control over a production CMS, omission of impact warnings increases the chance of unsafe use, accidental destructive actions, and over-broad delegation to an AI agent.
The configuration and capability sections instruct users to supply a bearer API key for remote administrative access to a WordPress site, but they do not warn about secure secret handling, the sensitivity of the token, or the risks of granting an AI agent broad remote admin functionality. This is dangerous because users may paste production credentials into insecure environments, overexpose highly privileged tokens, or connect agents to live sites without understanding the security implications.
No suspicious patterns detected.