Back to skill

Security audit

Appointment Booking System

Security checks for vulnerabilities and agentic risk

Overview

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.

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 (4)

T05 · Unauthorized Access and Privilege Escalation

Error
Location
workflows/02-booking-confirmation.json:5
Finding

Unauthenticated Booking Status Modification

Content
View full analysis
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Warning
Location
workflows/01-booking-intake.json:21
Finding

Stored HTML Injection in Client and Staff Emails

Content
View full analysis
New Appointment Booked
Booking ID{{ $json.booking_id }}
Client{{ $json.name }}
Email{{ $json.email }}
Phone{{ $json.phone }}
Service{{ $json.service }}
Date{{ $json.date }}
Time{{ $json.time }}
Notes
Remediation
View remediation
`, `"`, and `'`. 2. Use an email templating mechanism with automatic contextual escaping rather than directly building HTML with string interpolation. 3. Apply encoding in every workflow that produces HTML, including intake confirmation, staff notification, reminders, no-show follow-up, and daily schedules. 4. Validate fields against their intended formats: - Restrict dates and times to strict formats. - Validate phone numbers and email addresses. - Restrict service values to a server-controlled allowlist where possible. 5. Enforce conservative length limits for all booking fields, especially `notes`. 6. If limited formatting is required, sanitize it with a strict allowlist that excludes remote images, forms, style attributes, and unsafe URI schemes. 7. Sanitize historical rows already present in the sheet or guarantee that all values are escaped when rendered. 8. Add automated tests containing HTML metacharacters and malicious link/image payloads. ]]>

T09 · Insecure Skill Coding Practices

Warning
Location
workflows/01-booking-intake.json:5
Finding

Public Booking Intake Can Be Abused as an Email and Resource-Consumption Relay

Content
View full analysis
0) { return [{ json: { valid: false, errors } }]; } ``` Every accepted request can trigger an email to the submitted address: ```json { "parameters": { "sendTo": "={{ $json.email }}", "subject": "=Booking Confirmed — {{ $json.service }} on {{ $json.date }}", "message": "=

Booking Confirmation

Hi {{ $json.name }},

Your appointment has been confirmed:

Booking ID{{ $json.booking_id }}
Service{{ $json.service }}
Date{{ $json.date }}
Time{{ $json.time }}
", "options": {} }, "name": "Confirm to Client", "type": "n8n-nodes-base.emailSend" } ``` The saved booking also causes a staff notification: ```json "Save to Shee ...[truncated 2080 chars]
Remediation
View remediation

T09 · Insecure Skill Coding Practices

Warning
Location
workflows/01-booking-intake.json:21
Finding

Spreadsheet Formula Injection Through Booking Fields

Content
View full analysis
Remediation
View remediation
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • 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
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (13)

Ae1

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

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

md
| 03 | `03-reminder-engine.json` | Hourly check → send 24h and 2h reminders |

Ae1

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

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

md
| 04 | `04-noshow-followup.json` | Check past appointments → detect no-shows → followup email |

Missing User Warnings

High
Category
Not specified by scanner
Confidence
96% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

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.

Content

No source excerpt is available for this finding.

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 151)May include surrounding context.

4. Test Booking

bash
curl -X POST https://your-n8n.com/webhook/booking/new \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Jane Smith",

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
88% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
91% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
87% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
89% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Missing User Warnings

Medium
Category
Not specified by scanner
Confidence
86% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Missing User Warnings

Low
Category
Not specified by scanner
Confidence
81% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Vague Triggers

Low
Category
Not specified by scanner
Confidence
88% confidence
Finding

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.

Content

No source excerpt is available for this finding.

Natural-Language Policy Violations

Low
Category
Not specified by scanner
Confidence
95% confidence
Finding

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.

Content

No source excerpt is available for this finding.