<?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://db.gcve.eu</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>Sat, 17 Oct 2026 19:49:13 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-103366 — Appointment Booking Plugin &lt;= 5.7.3 - Insecure Direct Object Reference to Unauthenticated Sensitive Information Disclos…</title>
      <link>https://db.gcve.eu/vuln/cve-2026-103366</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; latepoint Appointment Booking Plugin – LatePoint | Calendar &amp;amp; Scheduling for WordPress&lt;/p&gt;
&lt;p&gt;The Appointment Booking Plugin – LatePoint | Calendar &amp;amp; Scheduling for WordPress plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 5.7.3 via the `booking[id]` and `cart[id]` parameters on the `steps__reload_booking_form_summary_panel` and `steps__start` public routes (reachable through wp_ajax_nopriv_latepoint_route_call). This is due to `OsStepsHelper::set_required_objects()` feeding raw request parameters into `set_booking_object()` and `set_cart_object()`, which call `OsModel::set_data()` and load an arbitrary booking or cart row by primary key with no ownership check — the ownership guard the vendor added for the earlier disclosure lives only inside `OsStepsHelper::load_step()` and does not cover the sibling routes or `cart[id]` at all. This makes it possible for unauthenticated attackers to enumerate sequential booking / cart identifiers and read other customers&amp;#39; appointment details (service name, agent, date/time, duration, price breakdown, status) and other shoppers&amp;#39; pending checkout contents directly from the JSON responses.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; latepoint Appointment Booking Plugin – LatePoint | Calendar &amp;amp; Scheduling for WordPress&lt;/p&gt;
&lt;p&gt;The Appointment Booking Plugin – LatePoint | Calendar &amp;amp; Scheduling for WordPress plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 5.7.3 via the `booking[id]` and `cart[id]` parameters on the `steps__reload_booking_form_summary_panel` and `steps__start` public routes (reachable through wp_ajax_nopriv_latepoint_route_call). This is due to `OsStepsHelper::set_required_objects()` feeding raw request parameters into `set_booking_object()` and `set_cart_object()`, which call `OsModel::set_data()` and load an arbitrary booking or cart row by primary key with no ownership check — the ownership guard the vendor added for the earlier disclosure lives only inside `OsStepsHelper::load_step()` and does not cover the sibling routes or `cart[id]` at all. This makes it possible for unauthenticated attackers to enumerate sequential booking / cart identifiers and read other customers&amp;#39; appointment details (service name, agent, date/time, duration, price breakdown, status) and other shoppers&amp;#39; pending checkout contents directly from the JSON responses.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-103366</guid>
    </item>
  </channel>
</rss>
