<?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>Thu, 01 Oct 2026 23:19:23 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-92966 — Appointment Booking Plugin &lt;= 5.7.0 - Unauthenticated Arbitrary Shortcode Execution via First/Last Name Field</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-92966</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 The Appointment Booking Plugin – LatePoint | Calendar &amp;amp; Scheduling for WordPress plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 5.7.0. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes. The payload is planted during the unauthenticated booking flow and triggered when the Customer Cabinet block rendered by render_customer_dashboard() outputs the stored name into the content stream, where WordPress core&amp;#39;s do_shortcode filter at priority 11 re-parses and executes it.&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 The Appointment Booking Plugin – LatePoint | Calendar &amp;amp; Scheduling for WordPress plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 5.7.0. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes. The payload is planted during the unauthenticated booking flow and triggered when the Customer Cabinet block rendered by render_customer_dashboard() outputs the stored name into the content stream, where WordPress core&amp;#39;s do_shortcode filter at priority 11 re-parses and executes it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-92966</guid>
    </item>
  </channel>
</rss>
