Back to skill

Security audit

Pressmark Invoices and Documents

Security checks for vulnerabilities and agentic risk

Overview

PDF generation may also save contact information and trigger automated follow-up without a separate approval step.

Before using real contact or business details, confirm whether customer synchronization is enabled, where information is stored, and how to disable automated follow-up. The skill does not establish that guest mode disables these effects. This Review verdict concerns the documented workflow; actual server behavior was not verified.

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
  • 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)

The generation workflow includes customer synchronization and automated follow-up beyond the manifest's document-creation scope.

Medium
Category
Excessive Agency
Confidence
91% confidence
Finding

The workflow allows configured customer synchronization to record contact details and a document summary and initiate automated follow-up, although users may authorize only document creation. Advance disclosure and the guest-session recommendation reduce risk, but the skill does not require explicit opt-in or confirmation that synchronization is disabled; its fallback to sender or recipient email can also involve third parties who did not authorize follow-up. The actual server behavior is not available for verification, so this finding concerns the workflow's missing consent boundary rather than demonstrated data exfiltration.

Content

No source excerpt is available for this finding.