Security audit

WordPress Receipts

Security checks for vulnerabilities and agentic risk

Overview

The skill is mostly coherent for WordPress publishing, but its receipt verifier can treat any HTTP 200 URL as success and the publisher posts live by default.

Review this before installing if you plan to rely on receipts for automation. Use API-based verification by post ID or date, avoid URL-only success checks, restrict the WordPress API base and credentials to the intended site, and consider defaulting posts to draft or requiring an explicit publish flag for unattended workflows.

A.I.G

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 (2)

T09 · Insecure Skill Coding Practices

Warning

Location: scripts/wp-verify-receipt.mjs:79
Finding: Unrestricted URL Fetch Enables Blind Server-Side Request Forgery
Content: View full analysis
Remediation: View remediation

T09 · Insecure Skill Coding Practices

Warning

Location: scripts/wp-verify-receipt.mjs:79
Finding: URL-Only Verification Accepts Unrelated HTTP 200 Pages as WordPress Publication Receipts
Content: View full analysis
Remediation: View remediation

SkillSpector

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (8)

Ae1

High

Category: analysis-evasion
Confidence: 100% confidence
Finding: Referenced artifact was not completely inspected
Content: Scanner excerpt · SKILL.md (reported line 62)May include surrounding context.
md
node scripts/wp-publish-receipt.mjs \

Ae1

High

Category: analysis-evasion
Confidence: 100% confidence
Finding: Referenced artifact was not completely inspected
Content: Scanner excerpt · SKILL.md (reported line 73)May include surrounding context.
md
node scripts/wp-verify-receipt.mjs --env-file .env.wordpress --date 2026-07-01

Ae1

High

Category: analysis-evasion
Confidence: 100% confidence
Finding: Referenced artifact was not completely inspected
Content: Scanner excerpt · SKILL.md (reported line 74)May include surrounding context.
md
node scripts/wp-verify-receipt.mjs --env-file .env.wordpress --date 2026-07-01

Ae1

High

Category: analysis-evasion
Confidence: 100% confidence
Finding: Referenced artifact was not completely inspected
Content: Scanner excerpt · SKILL.md (reported line 75)May include surrounding context.
md
node scripts/wp-verify-receipt.mjs --env-file .env.wordpress --date 2026-07-01

Ae1

High

Category: analysis-evasion
Confidence: 100% confidence
Finding: Referenced artifact was not completely inspected
Content: Scanner excerpt · SKILL.md (reported line 80)May include surrounding context.
md
node scripts/wp-verify-receipt.mjs --env-file .env.wordpress --date 2026-07-01

Ae1

High

Category: analysis-evasion
Confidence: 100% confidence
Finding: Referenced artifact was not completely inspected
Content: Scanner excerpt · SKILL.md (reported line 118)May include surrounding context.
md
node scripts/wp-verify-receipt.mjs --env-file .env.wordpress --date 2026-07-01

Undeclared Tool Scope

Medium

Category: MCP Least Privilege
Confidence: 89% confidence
Finding: The skill clearly instructs the use of network-capable helper scripts against the WordPress REST API, but it does not declare an explicit tool scope such as permissions or allowed-tools. In an agent environment, that mismatch weakens least-privilege controls and can allow broader-than-expected network use, making unintended outbound requests or abuse of stored credentials more likely.
Content: No source excerpt is available for this finding.

Missing User Warnings

Medium

Category: Not specified by scanner
Confidence: 91% confidence
Finding: This code defaults the post status to 'publish' and immediately sends a POST request to create the post, which is a user-data-affecting and externally visible operation. There is no confirmation prompt, warning message, or other user disclosure in the script before publication occurs.
Content: No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.