<?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 19:58:43 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-12956</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-12956</link>
      <description>&lt;p&gt;The WP Event Solution (Eventin) plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 4.1.22 via the create_item() handler for the /wp-json/eventin/v2/orders REST endpoint. The endpoint&amp;#39;s create_item_permissions_check() function only verifies a wp_rest nonce (which is leaked to every visitor through the etn-public script&amp;#39;s localized_data_obj on every frontend page) and accepts a user-supplied &amp;#39;status&amp;#39; value in prepare_item_for_database() with no whitelist validation. This makes it possible for unauthenticated attackers to create etn-order posts with status=&amp;#39;completed&amp;#39; that are counted as sold by etn_get_sold_tickets_by_event(); because the auto-cleanup wp_schedule_single_event() in create_item() only fires for status=&amp;#39;pending&amp;#39; orders, the forged completed orders persist indefinitely and exhaust ticket inventory.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The WP Event Solution (Eventin) plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 4.1.22 via the create_item() handler for the /wp-json/eventin/v2/orders REST endpoint. The endpoint&amp;#39;s create_item_permissions_check() function only verifies a wp_rest nonce (which is leaked to every visitor through the etn-public script&amp;#39;s localized_data_obj on every frontend page) and accepts a user-supplied &amp;#39;status&amp;#39; value in prepare_item_for_database() with no whitelist validation. This makes it possible for unauthenticated attackers to create etn-order posts with status=&amp;#39;completed&amp;#39; that are counted as sold by etn_get_sold_tickets_by_event(); because the auto-cleanup wp_schedule_single_event() in create_item() only fires for status=&amp;#39;pending&amp;#39; orders, the forged completed orders persist indefinitely and exhaust ticket inventory.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-12956</guid>
    </item>
    <item>
      <title>GHSA-wfw6-vjph-f3w6</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-wfw6-vjph-f3w6</link>
      <description>&lt;p&gt;The WP Event Solution (Eventin) plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 4.1.22 via the create_item() handler for the /wp-json/eventin/v2/orders REST endpoint. The endpoint&amp;#39;s create_item_permissions_check() function only verifies a wp_rest nonce (which is leaked to every visitor through the etn-public script&amp;#39;s localized_data_obj on every frontend page) and accepts a user-supplied &amp;#39;status&amp;#39; value in prepare_item_for_database() with no whitelist validation. This makes it possible for unauthenticated attackers to create etn-order posts with status=&amp;#39;completed&amp;#39; that are counted as sold by etn_get_sold_tickets_by_event(); because the auto-cleanup wp_schedule_single_event() in create_item() only fires for status=&amp;#39;pending&amp;#39; orders, the forged completed orders persist indefinitely and exhaust ticket inventory.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The WP Event Solution (Eventin) plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 4.1.22 via the create_item() handler for the /wp-json/eventin/v2/orders REST endpoint. The endpoint&amp;#39;s create_item_permissions_check() function only verifies a wp_rest nonce (which is leaked to every visitor through the etn-public script&amp;#39;s localized_data_obj on every frontend page) and accepts a user-supplied &amp;#39;status&amp;#39; value in prepare_item_for_database() with no whitelist validation. This makes it possible for unauthenticated attackers to create etn-order posts with status=&amp;#39;completed&amp;#39; that are counted as sold by etn_get_sold_tickets_by_event(); because the auto-cleanup wp_schedule_single_event() in create_item() only fires for status=&amp;#39;pending&amp;#39; orders, the forged completed orders persist indefinitely and exhaust ticket inventory.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-wfw6-vjph-f3w6</guid>
    </item>
  </channel>
</rss>
