T05 · Unauthorized Access and Privilege Escalation
- Location
openapi.json:115- Finding
Card Update and Deletion Operations Have No Declared Access Control
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
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.
openapi.json:115Card Update and Deletion Operations Have No Declared Access Control
openapi.json:199Analytics Endpoints Permit Undeclared Anonymous Retrieval and Event Manipulation
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).
---
### `DELETE /cards/{slug}`
**Summary:** Delete Card
**Description:** Permanently delete a digital business card and all associated data.
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.
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.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## References
- **Kong Route:** https://api.toolweb.in/tools/cardsnap
- **API Docs:** https://api.toolweb.in:8185/docs
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.
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.