Back to skill

Security audit

docspring-html-templates

Security checks for vulnerabilities and agentic risk

Overview

The scanners classify this skill as benign because the reported behavior appears aligned with working on DocSpring HTML templates, though the review was partial and confidence is medium.

The verdict is benign, but confidence is medium and Skillspector inspected only 2 of 3 components fully; one tool-misuse check was also partial. Before installing, consider whether you trust DocSpring with any data you submit for previews, and review the skill’s guidance yourself if complete scan coverage matters to you.

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
  • 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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (2)

Anti-Refusal Statement

High
Category
Anti-Refusal
Confidence
85% confidence
Finding

Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.

Content

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

md
1. **You edit the draft.** Until a template's first `publish_version`, its submissions use the draft, so every save
   is live. Once a version is published, submissions use the latest published version, and your edits reach the
   user's documents only after the next `publish_version`. Render the draft to test it: that needs no publish.
2. **Render after every change and look at every page.** Don't judge a layout from the HTML or from a local browser:
   DocSpring's renderer adds its own CSS, has its own fonts and prints with its own page settings.
3. **Preview, don't submit.** `preview_template` renders the draft with your data and returns PNG images of its pages,
   not a PDF, for free and without a submission. Make a test PDF (`generate_pdf` with `test: true`, free and watermarked) only to check something a preview can't

External Transmission

Medium
Category
Data Exfiltration
Confidence
60% confidence
Finding

Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Content

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

md
docspring templates previews create "$TEMPLATE_ID" --data '{"data": {"invoice_number": "INV-1001"}}' --json
docspring templates previews get "$TEMPLATE_ID" "$PREVIEW_ID" --json
# Without the CLI
curl -sS "https://sync.api.docspring.com/api/v2/templates/$TEMPLATE_ID/previews" \
  -u "$DOCSPRING_TOKEN_ID:$DOCSPRING_TOKEN_SECRET" -H 'Content-Type: application/json' \
  -d '{"data": {"invoice_number": "INV-1001"}}'
curl -sS "https://sync.api.docspring.com/api/v2/templates/$TEMPLATE_ID/previews/$PREVIEW_ID" \