https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 15 Oct 2026 22:57:59 +0000 https://db.gcve.eu/vuln/cve-2026-100163 <p><strong>Affected:</strong> latepoint Appointment Booking Plugin – LatePoint | Calendar &amp; Scheduling for WordPress</p> <p>The Appointment Booking Plugin – LatePoint | Calendar &amp; Scheduling for WordPress plugin for WordPress is vulnerable to Authentication Bypass in versions up to, and including, 5.7.2 via the OsCustomerHelper::create_wp_user_for_customer() helper reached from the public process_step_customer() booking step. When the &#39;Use WordPress users as customers&#39; option is enabled, the helper falls back from email_exists() to username_exists( $customer-&gt;email ), which matches any WordPress user whose user_login equals the victim customer&#39;s email even when that user&#39;s user_email is completely different, and links that WordPress user&#39;s ID into the victim&#39;s LatePoint customer row (only privileged roles are excluded; Subscriber is allowed). This makes it possible for authenticated attackers, with Subscriber-level access and above, to take over another customer&#39;s LatePoint account — accessing their bookings, service, agent, and calendar data, and having the victim customer&#39;s email overwritten with the attacker&#39;s on next login — by holding a Subscriber account whose user_login equals the victim&#39;s email and submitting an unauthenticated public booking step registration request.</p> <p><strong>Affected:</strong> latepoint Appointment Booking Plugin – LatePoint | Calendar &amp; Scheduling for WordPress</p> <p>The Appointment Booking Plugin – LatePoint | Calendar &amp; Scheduling for WordPress plugin for WordPress is vulnerable to Authentication Bypass in versions up to, and including, 5.7.2 via the OsCustomerHelper::create_wp_user_for_customer() helper reached from the public process_step_customer() booking step. When the &#39;Use WordPress users as customers&#39; option is enabled, the helper falls back from email_exists() to username_exists( $customer-&gt;email ), which matches any WordPress user whose user_login equals the victim customer&#39;s email even when that user&#39;s user_email is completely different, and links that WordPress user&#39;s ID into the victim&#39;s LatePoint customer row (only privileged roles are excluded; Subscriber is allowed). This makes it possible for authenticated attackers, with Subscriber-level access and above, to take over another customer&#39;s LatePoint account — accessing their bookings, service, agent, and calendar data, and having the victim customer&#39;s email overwritten with the attacker&#39;s on next login — by holding a Subscriber account whose user_login equals the victim&#39;s email and submitting an unauthenticated public booking step registration request.</p> https://db.gcve.eu/vuln/cve-2026-100163