<?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://cve.radiocsirt.org</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 19:14:39 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-11823 — BookingPress Appointment Booking Pro &lt;= 5.7.1 - Unauthenticated SQL Injection via 'store_service_date' Parameter</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-11823</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Repute Infosystems BookingPress Appointment Booking Pro&lt;/p&gt;
&lt;p&gt;The BookingPress Appointment Booking Pro plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;store_service_date&amp;#39; parameter of the bpa_assign_staffmember_to_slots() function in versions up to and including 5.7.1. This is due to the explicit use of stripslashes_deep() on user-supplied POST data before it is interpolated verbatim into a SQL LIKE clause without use of $wpdb-&amp;gt;prepare() or any parameterization. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Repute Infosystems BookingPress Appointment Booking Pro&lt;/p&gt;
&lt;p&gt;The BookingPress Appointment Booking Pro plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;store_service_date&amp;#39; parameter of the bpa_assign_staffmember_to_slots() function in versions up to and including 5.7.1. This is due to the explicit use of stripslashes_deep() on user-supplied POST data before it is interpolated verbatim into a SQL LIKE clause without use of $wpdb-&amp;gt;prepare() or any parameterization. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-11823</guid>
    </item>
  </channel>
</rss>
