<?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>Fri, 02 Oct 2026 15:19:39 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-14945 — Events Manager - Calendar, Bookings, Tickets, and more! &lt;= 7.3.3 - Unauthenticated Stored Cross-Site Scripting via Even…</title>
      <link>https://db.gcve.eu/vuln/cve-2025-14945</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; netweblogic Events Manager – Calendar, Bookings, Tickets, and more!&lt;/p&gt;
&lt;p&gt;The Events Manager - Calendar, Bookings, Tickets, and more! plugin for WordPress is vulnerable to Stored Cross-Site Scripting via event attribute values in all versions up to, and including, 7.3.3. This is due to insufficient input sanitization when storing attribute values (using only `wp_unslash()` without sanitization) and lack of output escaping when rendering the &amp;#39;#_ATT{key}&amp;#39; placeholder. This makes it possible for authenticated attackers, with Author-level access and above, or unauthenticated attackers when anonymous event submissions are enabled, to inject arbitrary web scripts that execute when any user views the affected event page.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; netweblogic Events Manager – Calendar, Bookings, Tickets, and more!&lt;/p&gt;
&lt;p&gt;The Events Manager - Calendar, Bookings, Tickets, and more! plugin for WordPress is vulnerable to Stored Cross-Site Scripting via event attribute values in all versions up to, and including, 7.3.3. This is due to insufficient input sanitization when storing attribute values (using only `wp_unslash()` without sanitization) and lack of output escaping when rendering the &amp;#39;#_ATT{key}&amp;#39; placeholder. This makes it possible for authenticated attackers, with Author-level access and above, or unauthenticated attackers when anonymous event submissions are enabled, to inject arbitrary web scripts that execute when any user views the affected event page.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2025-14945</guid>
    </item>
  </channel>
</rss>
