T09 · Insecure Skill Coding Practices
- Location
openapi.json:15- Finding
Financial Data Operations Lack Defined Authentication and Object-Level Authorization
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This finance API skill is purpose-aligned, but it documents sensitive financial read, export, update, and delete operations without clear authentication, ownership checks, or user safety warnings.
Review this skill carefully before installing or using it with real financial data. Only use it if you trust the ToolWeb service and can confirm the backend enforces authentication, per-user ownership checks, short-lived protected export links, and clear confirmation before destructive deletes.
openapi.json:15Financial Data Operations Lack Defined Authentication and Object-Level Authorization
A delete endpoint that accepts a transaction ID in the path and a userId in the body is a classic parameter-abuse risk area, especially in a finance context where records are sensitive and integrity matters. If the backend trusts caller-supplied identifiers without deriving user identity from authentication context and enforcing ownership checks, an attacker could delete another user's financial records through IDOR-style manipulation.
---
### DELETE /api/financy/transaction/{transaction_id}
**Delete Transaction**
Removes a specific transaction from the user's account.
This markdown file documents a transaction deletion capability that removes user financial records, but it does not include any warning about permanence, confirmation, or recovery limitations. For markdown files, omitting warnings about behaviors that can affect user data integrity qualifies as a missing user warning.
The skill description explains that user financial transaction data can be exported and made available via a download URL, but it provides no warning about sensitive financial data exposure, sharing, or retention considerations. For markdown files, omission of warnings about privacy-impacting behavior is in scope.
The skill returns a direct external download URL for exported transaction data, which means sensitive financial records may be transmitted or accessed outside the immediate tool interaction. If the URL is long-lived, predictable, or not bound to the authenticated user, it could enable unauthorized access or unintended sharing of personal financial data.
"success": true,
"export_id": "exp_12345",
"format": "csv",
"download_url": "https://api.toolweb.in/tools/financy/exports/exp_12345.csv",
"record_count": 42,
"generated_at": "2024-01-15T10:30:00Z"
}
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/financy
- **API Docs:** https://api.toolweb.in:8170/docs
The API exposes destructive deletion and sensitive export operations with no indication of confirmation requirements, user-consent safeguards, or warnings about the sensitivity of financial data. In a personal finance context, this increases the risk that an agent or user could unintentionally delete records or export private financial information without adequate friction or awareness.