Back to skill

Security audit

CardSnap

Security checks for vulnerabilities and agentic risk

Overview

CardSnap is a coherent business-card API skill, but its documented API allows card updates, permanent deletion, and analytics access without declared authentication, ownership checks, or privacy controls.

Review before installing or using this skill with real card data. Only use it if you are comfortable sending contact/profile data to ToolWeb and can verify that the live service enforces authentication, ownership checks, consent/privacy handling, rate limits, and a safe confirmation or recovery path for deletion.

Vulnerability Patterns
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • 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
Findings (2)

T05 · Unauthorized Access and Privilege Escalation

Error
Location
openapi.json:115
Finding

Card Update and Deletion Operations Have No Declared Access Control

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Warning
Location
openapi.json:199
Finding

Analytics Endpoints Permit Undeclared Anonymous Retrieval and Event Manipulation

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (6)

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
80% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

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

md
---

### `DELETE /cards/{slug}`
**Summary:** Delete Card

**Description:** Permanently delete a digital business card and all associated data.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

This markdown file documents recording engagement events and retrieving analytics, including views, saves, shares, and timestamps, but does not provide any user warning about collection of usage data or privacy impact. For markdown files, SQP-2 applies when the skill description omits warnings about behaviors that could affect user data or privacy.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The documentation states that DELETE /cards/{slug} will permanently delete a digital business card and all associated data, but it does not include any warning or caution about irreversibility. For markdown files, destructive behaviors affecting user data should be accompanied by an explicit warning.

Content

No source excerpt is available for this finding.

External Transmission

Medium
Category
Data Exfiltration
Confidence
50% 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 261)May include surrounding context.

md
## References

- **Kong Route:** https://api.toolweb.in/tools/cardsnap
- **API Docs:** https://api.toolweb.in:8185/docs

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
93% confidence
Finding

The API exposes analytics tracking and retrieval endpoints for card view/save/share events, but the specification provides no indication of consent controls, data minimization, retention limits, or restrictions on when tracking may occur. In a digital business card product, this creates a real privacy risk because user interaction data may be collected and disclosed without clear authorization or scope limitations.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Medium
Category
Not specified by scanner
Confidence
90% confidence
Finding

The natural-language descriptions say the service will 'track card view/save/share events' and 'get analytics for a card' without mentioning user notice, choice, or consent. Even if implementation details are absent, this omission in an analytics-focused feature strongly suggests privacy-sensitive behavior may be normalized or integrated without adequate transparency, increasing compliance and abuse risk.

Content

No source excerpt is available for this finding.