<?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>Mon, 28 Sep 2026 20:21:51 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-18441 — LatePoint - Appointment Booking &amp; Scheduling &lt;= 5.6.9 - Unauthenticated Insecure Direct Object Reference to Sensitive I…</title>
      <link>https://db.gcve.eu/vuln/cve-2026-18441</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 all versions up to, and including, 5.6.9  via the set_customer_object due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to enumerate arbitrary customer records and disclose personally identifiable information -  including first name, last name, email address, and phone number - by iterating the customer[id] parameter. This issue is exploitable only when the site is configured with customer authentication disabled (guest checkout enabled).&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 all versions up to, and including, 5.6.9  via the set_customer_object due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to enumerate arbitrary customer records and disclose personally identifiable information -  including first name, last name, email address, and phone number - by iterating the customer[id] parameter. This issue is exploitable only when the site is configured with customer authentication disabled (guest checkout enabled).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-18441</guid>
    </item>
  </channel>
</rss>
