<?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>Sun, 18 Oct 2026 09:43:32 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-2893 — Page and Post Clone &lt;= 6.3 - Authenticated (Contributor+) SQL Injection via 'meta_key' Parameter</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-2893</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; carlosfazenda Fast Page &amp;amp; Post Duplicator&lt;/p&gt;
&lt;p&gt;The Page and Post Clone plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;meta_key&amp;#39; parameter in the content_clone() function in all versions up to, and including, 6.3. This is due to insufficient escaping on the user-supplied meta_key value and insufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The injection is second-order: the malicious payload is stored as a post meta key and executed when the post is cloned.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; carlosfazenda Fast Page &amp;amp; Post Duplicator&lt;/p&gt;
&lt;p&gt;The Page and Post Clone plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;meta_key&amp;#39; parameter in the content_clone() function in all versions up to, and including, 6.3. This is due to insufficient escaping on the user-supplied meta_key value and insufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The injection is second-order: the malicious payload is stored as a post meta key and executed when the post is cloned.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-2893</guid>
    </item>
  </channel>
</rss>
