<?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 10:08:28 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-121151 — UpdraftPlus (Free &amp; Pro) - Subscriber+ PHP Object Injection via Database Restore Whitespace Trimming</title>
      <link>https://db.gcve.eu/vuln/cve-2026-121151</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Unknown UpdraftPlus: WP Backup &amp;amp; Migration Plugin&lt;/p&gt;
&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 preserve long database values byte-for-byte when restoring a database backup, allowing users with a role as low as Subscriber to plant a serialized value that becomes a PHP Object Injection once an administrator backs up and restores the database.&lt;/p&gt;
&lt;p&gt;No gadget chain is known in 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 or WordPress core, so the demonstrated effect is instantiation of an attacker-chosen class in the attacker&amp;#39;s own requests. Exploitation requires the planted data to line up exactly with how the backup is read back, which depends on details of the attacker&amp;#39;s row and the database dump format.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Unknown UpdraftPlus: WP Backup &amp;amp; Migration Plugin&lt;/p&gt;
&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 preserve long database values byte-for-byte when restoring a database backup, allowing users with a role as low as Subscriber to plant a serialized value that becomes a PHP Object Injection once an administrator backs up and restores the database.&lt;/p&gt;
&lt;p&gt;No gadget chain is known in 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 or WordPress core, so the demonstrated effect is instantiation of an attacker-chosen class in the attacker&amp;#39;s own requests. Exploitation requires the planted data to line up exactly with how the backup is read back, which depends on details of the attacker&amp;#39;s row and the database dump format.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-121151</guid>
    </item>
  </channel>
</rss>
