<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 20:38:47 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-48081 — OpenReception vulnerable to stored click-triggered XSS via javascript: tenant links rendered into patient-facing footer</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-48081</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; open-reception appointment-booking-software&lt;/p&gt;
&lt;p&gt;OpenReception&amp;#39;s appointment booking software provides an end-to-end encrypted appointment booking platform. Prior to version 1.0.2, a TENANT_ADMIN can store `javascript:` URLs in the tenant `links` configuration (`website`, `imprint`, `privacyStatement`). These values are returned to the patient-facing landing page via `/api/public`, hydrated into the SvelteKit Button component, and rendered as `&amp;lt;a href=&amp;#34;javascript:...&amp;#34;&amp;gt;` elements without URL-scheme filtering. A patient who clicks any such link executes the attacker&amp;#39;s JavaScript inside the patient browser origin, where patient form data is read before client-side encryption is applied. This breaks the project&amp;#39;s central trust claim that the server is an untrusted relay and that administrators cannot read patient data. Patient-side encryption happens after form input, so JavaScript executing in the patient origin can read or alter the plaintext before encryption is performed. Version 1.0.2 fixes the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; open-reception appointment-booking-software&lt;/p&gt;
&lt;p&gt;OpenReception&amp;#39;s appointment booking software provides an end-to-end encrypted appointment booking platform. Prior to version 1.0.2, a TENANT_ADMIN can store `javascript:` URLs in the tenant `links` configuration (`website`, `imprint`, `privacyStatement`). These values are returned to the patient-facing landing page via `/api/public`, hydrated into the SvelteKit Button component, and rendered as `&amp;lt;a href=&amp;#34;javascript:...&amp;#34;&amp;gt;` elements without URL-scheme filtering. A patient who clicks any such link executes the attacker&amp;#39;s JavaScript inside the patient browser origin, where patient form data is read before client-side encryption is applied. This breaks the project&amp;#39;s central trust claim that the server is an untrusted relay and that administrators cannot read patient data. Patient-side encryption happens after form input, so JavaScript executing in the patient origin can read or alter the plaintext before encryption is performed. Version 1.0.2 fixes the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-48081</guid>
    </item>
  </channel>
</rss>
