wordpress-theme

Security checks across malware telemetry and agentic risk

Overview

The skill appears to be coherent guidance material, with one documentation-quality security issue but no evidence of hidden execution, persistence, exfiltration, or destructive behavior.

This looks acceptable to install, but treat its WordPress security examples as guidance to review rather than authoritative policy. When using generated WordPress code, separately verify escaping and sanitization for custom fields, attributes, URLs, IDs, and arbitrary user-controlled output.

SkillSpector

By NVIDIA

Vulnerability Patterns

MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (1)

Intent-Code Divergence

Medium

Confidence: 90% confidence
Finding: This is a real security weakness in the guidance: the skill’s checklist claims all HTML output should be escaped, yet earlier template examples render content with `the_content()` directly. In WordPress, post content is intentionally HTML-capable and filtered by core, so this is not automatically exploitable on its own, but presenting contradictory guidance can lead developers to mishandle other dynamic fields and misunderstand when sanitization, escaping, or KSES controls are required.

VirusTotal

65/65 vendors flagged this skill as clean.

View on VirusTotal