<?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:26 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-121154</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-121154</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 keep serialized string lengths consistent when their database search and replace processes certain serialized values, allowing users with a role as low as Subscriber to plant data that becomes an attacker-chosen PHP object after an administrator runs a URL-lengthening search and replace or a migration restore.&lt;/p&gt;
&lt;p&gt;When the replacement changes the length of the text, the declared string lengths inside the stored value no longer match and the corrupted value is written back, so when WordPress later reads it the trailing bytes are parsed as further serialized structure, including an object of a class the attacker named. 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 themselves; further impact depends on classes available from other installed code.&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 keep serialized string lengths consistent when their database search and replace processes certain serialized values, allowing users with a role as low as Subscriber to plant data that becomes an attacker-chosen PHP object after an administrator runs a URL-lengthening search and replace or a migration restore.&lt;/p&gt;
&lt;p&gt;When the replacement changes the length of the text, the declared string lengths inside the stored value no longer match and the corrupted value is written back, so when WordPress later reads it the trailing bytes are parsed as further serialized structure, including an object of a class the attacker named. 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 themselves; further impact depends on classes available from other installed code.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-121154</guid>
    </item>
    <item>
      <title>GHSA-7pxf-q635-2wxc</title>
      <link>https://db.gcve.eu/vuln/ghsa-7pxf-q635-2wxc</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 keep serialized string lengths consistent when their database search and replace processes certain serialized values, allowing users with a role as low as Subscriber to plant data that becomes an attacker-chosen PHP object after an administrator runs a URL-lengthening search and replace or a migration restore.&lt;/p&gt;
&lt;p&gt;When the replacement changes the length of the text, the declared string lengths inside the stored value no longer match and the corrupted value is written back, so when WordPress later reads it the trailing bytes are parsed as further serialized structure, including an object of a class the attacker named. 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 themselves; further impact depends on classes available from other installed code.&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 keep serialized string lengths consistent when their database search and replace processes certain serialized values, allowing users with a role as low as Subscriber to plant data that becomes an attacker-chosen PHP object after an administrator runs a URL-lengthening search and replace or a migration restore.&lt;/p&gt;
&lt;p&gt;When the replacement changes the length of the text, the declared string lengths inside the stored value no longer match and the corrupted value is written back, so when WordPress later reads it the trailing bytes are parsed as further serialized structure, including an object of a class the attacker named. 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 themselves; further impact depends on classes available from other installed code.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-7pxf-q635-2wxc</guid>
    </item>
  </channel>
</rss>
