ClawHub
Back to skill

Security audit

Odoo

Security checks for vulnerabilities and agentic risk

Overview

This is a coherent Odoo operations skill that discloses its ERP access risks and repeatedly requires read-before-write review and user confirmation for sensitive changes.

Install this if you want an agent to help with Odoo operations. Before using it on production data, set clear read/write and approval boundaries, keep broad activation preferences narrow, and require previews plus explicit confirmation for imports, bulk changes, accounting corrections, inventory fixes, and API writes.

A.I.G

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

SkillSpector

Vulnerability Patterns
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (5)

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
85% confidence
Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

Scanner excerpt · SKILL.md (reported line 154)May include surrounding context.

md
- only the Odoo instance and export targets already involved in the user's task

**This skill does NOT:**
- bypass approvals for destructive writes or sensitive financial corrections
- store passwords, tokens, session cookies, or raw export payloads in memory
- assume a production write path when a safer review path exists
- make undeclared network requests by itself

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The instruction says to use this file when the user asks for 'something vague,' which is an ambiguous and very broad activation condition. It does not define clear boundaries, trigger phrases, or exclusion cases, so it could cause the skill to be used for many ordinary requests beyond its intended scope.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
96% confidence
Finding

The setup instructs the skill to activate on very broad business terms such as "ERP," "invoices," "sales orders," "stock," and "purchasing," and to persist that preference in memory for future sessions. This can cause the Odoo skill to trigger in unrelated or only tangentially related contexts, increasing the chance of inappropriate tool use, overscoped data access, or unsafe write-oriented behavior in a live business system.

Content

No source excerpt is available for this finding.

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
94% confidence
Finding

The trigger phrase includes the broad everyday expression "Odoo is wrong," which can match many normal user complaints and invoke the skill in situations far outside narrowly scoped Odoo triage. Overly broad triggers increase the chance of accidental activation, causing the agent to act on ambiguous requests and potentially expose or modify business data in an ERP context.

Content

No source excerpt is available for this finding.

Vague Triggers

Low
Category
Not specified by scanner
Confidence
90% confidence
Finding

The activation guidance says to use this file when the user wants dashboards, summaries, exports, or executive numbers from Odoo, but it does not define clearer boundaries or exclusions. Terms like "summaries" and "exports" are broad enough to match many ordinary requests, which can make invocation scope ambiguous.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.