/

CVE-2026-48081

Severity:

HIGH RISK

(8.1)

Stored XSS (CWE-79) in OpenReception Appointment App

CVE-2026-48081

Deferred

Vulnerability type

Category:

Stored Cross-Site Scripting

CWE:

CWE-79

Impact:

Client-Side Code Execution and Patient Data Exposure

Severity:

HIGH RISK

(8.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

OpenReception stores tenant-controlled link values and renders them on the patient-facing landing page without filtering unsafe URL schemes. A patient who clicks a malicious link may execute JavaScript in the application origin, allowing plaintext form data to be read or altered before client-side encryption occurs.

Affected context

The vulnerability can occur in deployments where a tenant administrator with permission to manage tenant links can save attacker-controlled URL values in the website, imprint, or privacy-statement configuration. Those values are exposed through the public API and rendered as anchor destinations in the patient-facing SvelteKit interface without adequate URL-scheme validation.

Exploit preconditions

  • Attack surface: Patient-facing landing-page links
  • Required access: Permission to modify the affected tenant link configuration, such as TENANT_ADMIN access
  • Trigger point: A patient clicks a configured link rendered by the landing page
  • Why exploitation is possible: The application accepts and renders unsafe URL schemes, allowing script execution in the patient browser origin
  • Data condition: Patient information must be entered or otherwise available in the page before client-side encryption is performed

Why this happens

The root cause is insufficient output and URL-scheme validation for tenant-controlled link values. Treating configuration data as a safe navigation target allows attacker-controlled content to become executable browser code when placed in an anchor destination.

This maps to CWE-79: Improper Neutralization of Input During Web Page Generation, because untrusted data reaches an HTML-rendering component without enforcing an allowlist of non-executable URL schemes or applying an equivalent safe-link policy. Client-side encryption does not prevent compromise when malicious code executes before plaintext data is encrypted.

Potential impact

  • An attacker may read patient form data before encryption
  • Malicious code could alter or suppress submitted patient information
  • Patient sessions may be abused within the affected application origin
  • Confidentiality of appointment-related information may be compromised
  • The platform's server-untrusted-relay trust model could be undermined

General mitigation guidance

Mitigation generally focuses on treating tenant link settings as untrusted input throughout the application lifecycle.

Common defensive patterns include:

  • Allowlisting safe URL schemes such as HTTPS and, where appropriate, HTTP
  • Rejecting executable or browser-interpreted schemes during validation and again before rendering
  • Rendering external destinations through safe, constrained link components
  • Applying contextual output encoding and framework-supported attribute escaping
  • Separating administrative configuration from executable client-side behavior
  • Limiting tenant administration privileges and reviewing changes to public-facing links
  • Enforcing a restrictive Content Security Policy as defense in depth
  • Minimizing sensitive data exposure to browser scripts and preserving encryption boundaries where practical

How teams detect issues like this

Organizations can detect similar issues through:

  • Static analysis rules for user-controlled values reaching HTML attributes or link components
  • Code review checks for dynamic href or URL construction without scheme allowlisting
  • Tests covering malicious and unexpected URL schemes in tenant configuration fields
  • Browser-based security testing that verifies rendered links cannot execute script code
  • Policy enforcement requiring centralized safe-link validation for public-facing URLs
  • Automated security review tools that identify stored input flowing into client-side navigation elements

Sources

SourceLink
github.comgithub.com/open-reception/appointment-booking-software/commit/98a107d4b4eaeab5cbb96ee0a28c2342b853eee0
github.comgithub.com/open-reception/appointment-booking-software/security/advisories/GHSA-xpr7-wx69-mp36

Frequently asked

questions

Exploitation generally requires a user with tenant administration privileges or equivalent ability to modify the affected link configuration, followed by a patient clicking the resulting link.

It may. JavaScript executing in the patient browser origin can observe or modify plaintext form data before the application performs client-side encryption.

Validate link destinations with a strict allowlist of safe URL schemes, reject executable schemes, and apply the same checks immediately before rendering user-controlled links.

Treat administrative configuration as untrusted, centralize safe URL handling, test all user-controlled navigation paths, use restrictive browser security policies, and review whether sensitive data is exposed to page scripts before encryption.

Find out what's already
exploitable in your codebase.