<?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>Sat, 21 Nov 2026 09:56:23 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-121150</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-121150</link>
      <description>&lt;p&gt;The UpdraftPlus: WP Backup &amp;amp; Migration Plugin WordPress plugin before 2.26.16.26, UpdraftPlus: WP Backup &amp;amp; Migration Plugin WordPress plugin before 1.26.16 do not correctly handle comment-like content found in the middle of a long SQL statement when restoring a database backup, allowing users with a role as low as Subscriber who have stored crafted content in their own profile to have SQL executed when an administrator later restores a backup, and so escalate their account to administrator.&lt;/p&gt;
&lt;p&gt;This is a different code path from the backup restore issue fixed in 1.26.10, and it does not depend on the database server&amp;#39;s maximum packet size.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The UpdraftPlus: WP Backup &amp;amp; Migration Plugin WordPress plugin before 2.26.16.26, UpdraftPlus: WP Backup &amp;amp; Migration Plugin WordPress plugin before 1.26.16 do not correctly handle comment-like content found in the middle of a long SQL statement when restoring a database backup, allowing users with a role as low as Subscriber who have stored crafted content in their own profile to have SQL executed when an administrator later restores a backup, and so escalate their account to administrator.&lt;/p&gt;
&lt;p&gt;This is a different code path from the backup restore issue fixed in 1.26.10, and it does not depend on the database server&amp;#39;s maximum packet size.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-121150</guid>
    </item>
    <item>
      <title>GHSA-2rv6-4rr6-fr26</title>
      <link>https://db.gcve.eu/vuln/ghsa-2rv6-4rr6-fr26</link>
      <description>&lt;p&gt;The UpdraftPlus: WP Backup &amp;amp; Migration Plugin WordPress plugin before 2.26.16.26, UpdraftPlus: WP Backup &amp;amp; Migration Plugin WordPress plugin before 1.26.16 do not correctly handle comment-like content found in the middle of a long SQL statement when restoring a database backup, allowing users with a role as low as Subscriber who have stored crafted content in their own profile to have SQL executed when an administrator later restores a backup, and so escalate their account to administrator.&lt;/p&gt;
&lt;p&gt;This is a different code path from the backup restore issue fixed in 1.26.10, and it does not depend on the database server&amp;#39;s maximum packet size.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The UpdraftPlus: WP Backup &amp;amp; Migration Plugin WordPress plugin before 2.26.16.26, UpdraftPlus: WP Backup &amp;amp; Migration Plugin WordPress plugin before 1.26.16 do not correctly handle comment-like content found in the middle of a long SQL statement when restoring a database backup, allowing users with a role as low as Subscriber who have stored crafted content in their own profile to have SQL executed when an administrator later restores a backup, and so escalate their account to administrator.&lt;/p&gt;
&lt;p&gt;This is a different code path from the backup restore issue fixed in 1.26.10, and it does not depend on the database server&amp;#39;s maximum packet size.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-2rv6-4rr6-fr26</guid>
    </item>
  </channel>
</rss>
