<?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 07:23:33 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-84693 — WPvivid — Backup, Migration &amp; Staging &lt;= 0.9.134 - Unauthenticated Arbitrary File Deletion via Migration Receiver and B…</title>
      <link>https://db.gcve.eu/vuln/cve-2026-84693</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; wpvividplugins WPvivid — Backup, Migration &amp;amp; Staging&lt;/p&gt;
&lt;p&gt;The WPvivid — Backup, Migration &amp;amp; Staging plugin for WordPress is vulnerable to Arbitrary File Deletion in version up to, and including, 0.9.134. This is due to a timing side channel in the bundled RSA decryption path, insufficient validation of migration receiver backup records, and missing path validation in the cleanup_local_backup() function. This makes it possible for unauthenticated attackers to recover an active migration receiver&amp;#39;s RSA modulus, inject a backup record containing path traversal, and cause a later scheduled cleanup to delete an attacker-selected file writable by the web server. Exploitation requires an unexpired receiver key generated by an administrator and a subsequent manual or scheduled backup lifecycle.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; wpvividplugins WPvivid — Backup, Migration &amp;amp; Staging&lt;/p&gt;
&lt;p&gt;The WPvivid — Backup, Migration &amp;amp; Staging plugin for WordPress is vulnerable to Arbitrary File Deletion in version up to, and including, 0.9.134. This is due to a timing side channel in the bundled RSA decryption path, insufficient validation of migration receiver backup records, and missing path validation in the cleanup_local_backup() function. This makes it possible for unauthenticated attackers to recover an active migration receiver&amp;#39;s RSA modulus, inject a backup record containing path traversal, and cause a later scheduled cleanup to delete an attacker-selected file writable by the web server. Exploitation requires an unexpired receiver key generated by an administrator and a subsequent manual or scheduled backup lifecycle.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-84693</guid>
    </item>
  </channel>
</rss>
