<?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>Wed, 21 Oct 2026 21:01:17 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-3523 — Apocalypse Meow &lt;= 22.1.0 - Authenticated (Administrator+) SQL Injection via 'type' Parameter</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-3523</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; blobfolio Apocalypse Meow&lt;/p&gt;
&lt;p&gt;The Apocalypse Meow plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;type&amp;#39; parameter in all versions up to, and including, 22.1.0. This is due to a flawed logical operator in the type validation check on line 261 of ajax.php — the condition uses `&amp;amp;&amp;amp;` (AND) instead of `||` (OR), causing the `in_array()` validation to be short-circuited and never evaluated for any non-empty type value. Combined with `stripslashes_deep()` being called on line 101 which removes `wp_magic_quotes()` protection, attacker-controlled single quotes pass through unescaped into the SQL query on line 298. This makes it possible for authenticated attackers, with Administrator-level access and above, 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; blobfolio Apocalypse Meow&lt;/p&gt;
&lt;p&gt;The Apocalypse Meow plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;type&amp;#39; parameter in all versions up to, and including, 22.1.0. This is due to a flawed logical operator in the type validation check on line 261 of ajax.php — the condition uses `&amp;amp;&amp;amp;` (AND) instead of `||` (OR), causing the `in_array()` validation to be short-circuited and never evaluated for any non-empty type value. Combined with `stripslashes_deep()` being called on line 101 which removes `wp_magic_quotes()` protection, attacker-controlled single quotes pass through unescaped into the SQL query on line 298. This makes it possible for authenticated attackers, with Administrator-level access and above, 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-3523</guid>
    </item>
  </channel>
</rss>
