← Back to Scanner

wordpress Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower
Source:
SHA-256:

wordpress is an AI agent skill, created by ClawHub Skill. ClawSecure audited wordpress across 3 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 90/100 (Safe). The 3 findings concentrate in Data Exfiltration, Permissions Manifest and Policy Violation, including Code block in SKILL.md at line 620 contains potentially… and Missing config.json - agent may not be properly configured. None were rated high or critical severity.

Is wordpress safe?

ClawSecure audited wordpress and assigned a security score of 90/100 (Safe), identifying 3 findings across Data Exfiltration and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in wordpress?

ClawSecure identified 3 findings in wordpress, concentrated in Data Exfiltration, Permissions Manifest and Policy Violation. The most severe include Code block in SKILL.md at line 620 contains potentially… and Missing config.json - agent may not be properly configured.

How was wordpress audited?

ClawSecure ran wordpress through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 3 files.

What does a score of 90 mean?

ClawSecure assigned wordpress a security score of 90/100, placing it in the Safe range. Scores of 80 or above qualify for ClawSecure Verified status; the 3 findings detected are lower-severity. ClawSecure derives this score with a weighted deduction model (critical -20, high -10, medium -5, low -2 from a base of 100).

Audit Findings for wordpress

ClawSecure detected 3 security findings in wordpress, spanning Data Exfiltration, Permissions Manifest and Policy Violation.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for wordpress

Audit external network connections
wordpress sends data to external endpoints. Confirm each destination is expected and authorized, and remove any callback that exfiltrates data. ClawSecure monitors for known exfiltration and C2 endpoints.
Add a config.json permissions manifest
A config.json file declares what an agent component can access: file system, network, shell execution and more. Without it, users have no visibility into what the component can do before installing. This is the single most impactful security improvement for any AI agent skill.
Resolve policy violations
wordpress trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.
Pin dependencies to exact versions
Unpinned dependencies allow supply-chain attacks where a compromised version is pulled in automatically. Use exact version numbers in package.json (for example 1.2.3 instead of ^1.2.3) to keep unauthorized code out of your dependency tree. ClawSecure checks every dependency against known CVE databases.

Related Security Research

ClawHavoc Explained: The Malware Family Targeting AI AgentsBeyond Static Scans: Why ClawSecure Verifies Agentic IntentHow to Secure an MCP Server: The 2026 Guide

Related AI Agent Security Audits

snipara-mcpScore 85/100wacliScore 95/10019af8eafb16b72f6Score 75/10025937fcc251c4ccbScore 85/100b4abd97bcb77151aScore 75/100

Scanned on March 27, 2026. wordpress is one of thousands of agents audited by ClawSecure from the community-curated awesome-openclaw-skills list and the openclaw/skills repository.

Start Your Free Scan