Back to skill

Security audit

Flatsome Wordpress

Security checks for vulnerabilities and agentic risk

Overview

This is a mostly coherent WordPress/Flatsome site-building skill, but it gives admin-level WP-CLI instructions including irreversible page deletion without clear safeguards.

Review before installing if you will let an agent run WP-CLI commands. Use backups and staging, confirm the target WordPress path and post IDs, prefer trashing posts over `--force`, and approve plugin installs, theme changes, and published-content changes explicitly.

Vulnerability Patterns
  • 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
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (4)

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The heading and all operational instructions are presented in Vietnamese for 'mọi AI Agent', implying a fixed language behavior rather than a user-selected locale. There is no statement that the skill is Vietnam-specific or that users may choose another language.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The documentation explicitly states that output must avoid raw HTML, yet the contact/map example later uses a [ux_html] block containing a literal . This is an active contradiction between the stated implementation rule and the provided implementation pattern, not merely an omitted detail.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The skill includes a force-delete command (wp post delete PAGE_ID --force) with no confirmation, backup, scope validation, or warning. In an agent-execution context, this can lead to irreversible content loss from accidental misuse, bad variable substitution, or unsafe automation paths.

Content

No source excerpt is available for this finding.

Intent-Code Divergence

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The handoff checklist asserts a strict no-raw-HTML requirement, but earlier examples include raw HTML inside shortcode wrappers, such as the Google Maps iframe and CF7 form content wrapped in div tags. That creates a direct contradiction between the documented acceptance criteria and the actual recommended implementation.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.