T05 · Unauthorized Access and Privilege Escalation
- Location
workflows/02-booking-confirmation.json:5- Finding
Unauthenticated Booking Status Modification
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill matches an appointment-booking purpose, but its public n8n webhooks can send email and change booking records with too little authentication, validation, and privacy guidance.
Install only after adding authentication or signed expiring tokens for status changes, rate limiting and anti-abuse controls for public intake, strict field validation and length limits, HTML and spreadsheet-formula escaping, and a clear privacy/retention policy for customer data. Use least-privilege Google Sheets and SMTP credentials and test with non-production data first.
workflows/02-booking-confirmation.json:5Unauthenticated Booking Status Modification
workflows/01-booking-intake.json:21Stored HTML Injection in Client and Staff Emails
| Booking ID | {{ $json.booking_id }} |
| Client | {{ $json.name }} |
| {{ $json.email }} | |
| Phone | {{ $json.phone }} |
| Service | {{ $json.service }} |
| Date | {{ $json.date }} |
| Time | {{ $json.time }} |
| Notes |
workflows/01-booking-intake.json:5Public Booking Intake Can Be Abused as an Email and Resource-Consumption Relay
Hi {{ $json.name }},
Your appointment has been confirmed:
| Booking ID | {{ $json.booking_id }} |
| Service | {{ $json.service }} |
| Date | {{ $json.date }} |
| Time | {{ $json.time }} |
workflows/01-booking-intake.json:21Spreadsheet Formula Injection Through Booking Fields
Referenced artifact was not completely inspected
| 03 | `03-reminder-engine.json` | Hourly check → send 24h and 2h reminders |
Referenced artifact was not completely inspected
| 04 | `04-noshow-followup.json` | Check past appointments → detect no-shows → followup email |
This workflow collects, stores, and transmits sensitive personal data including name, email, phone, booking details, and freeform notes to Google Sheets and over email, but it contains no visible consent, minimization, retention, or sanitization controls. In this context, the skill is explicitly a production booking system, so handling customer PII without privacy safeguards or limiting untrusted content in emails/notes materially increases privacy, compliance, and data exposure risk.
The skill processes and stores personal data including names, emails, phone numbers, appointment dates, and notes, and transmits that data through webhooks, Google Sheets, and SMTP. The documentation does not warn users about privacy, consent, retention, or regulatory considerations, which increases the risk of unsafe deployment and inadvertent mishandling of PII.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -X POST https://your-n8n.com/webhook/booking/new \
-H "Content-Type: application/json" \
-d '{
"name": "Jane Smith",
This JSON manifest defines activation via a public webhook path of "booking/new" but provides no additional scope, context, or exclusion conditions describing when this workflow should or should not be invoked. For a manifest/config file, that broad trigger surface can lead to unintended or unauthorized activation because the trigger is not narrowly constrained in the file itself.
This workflow performs a persistent data write by updating booking status records in Google Sheets after receiving a webhook request. In this JSON file there is no visible confirmation step, user-facing log/message, or inline documentation warning that incoming requests will modify stored booking data.
This code-path sends emails to customer addresses using names, appointment details, and business contact information, which is a network operation transmitting user data. The workflow contains no confirmation step, user-facing log/print, or explanatory comment/docstring warning that customer data will be sent externally via SMTP.
The workflow sends emails to customer addresses and includes personal and appointment details such as name, service, date, and time. In this JSON file there is no confirmation step, user-facing notice, or descriptive comment warning that customer data will be transmitted via SMTP.
This step writes back to Google Sheets and changes status fields to 'no-show' while recording a follow-up timestamp, which affects business records and may be difficult to undo cleanly. The file does not include a confirmation mechanism, user-facing log, or explanatory documentation warning that records will be modified automatically.
This step writes back to Google Sheets by setting reminder status fields, which modifies user data. Although this is part of the workflow logic, the file provides no comment or user-facing disclosure that appointment records will be altered as reminders are processed.
This JSON manifest defines activation only as a cron expression running every day at 7:00, but provides no additional scope, negative examples, or contextual limits for when this workflow should or should not be used. Under the vague-trigger rule for manifest files, this is an ambiguous activation condition because the invocation intent is not further constrained in human-readable terms.
The workflow hard-codes English phrases such as 'Today', 'Tomorrow', 'Daily Schedule Report', and 'No appointments scheduled' in generated content. Because there is no opt-in or locale selection mechanism, this is a language-policy issue under the natural-language policy rule.