<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-19T21:23:50.748037+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2026-120391</id>
    <title>CVE-2026-120391 — WPvivid Backup &amp; Migration &lt; 0.9.140 - Subscriber+ PHP Object Injection via Migration Search and Replace</title>
    <updated>2026-11-19T21:23:50.752526+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Unknown WPvivid — Backup, Migration &amp; Staging</p>
<p>The WPvivid — Backup, Migration &amp; Staging WordPress plugin before 0.9.140 does not prevent serialized data it cannot safely unserialize from being re-serialized as a PHP object during a site migration, allowing users with a role as low as Subscriber to plant a PHP object that WordPress instantiates after an administrator restores a backup onto a different URL.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-120391"/>
  </entry>
</feed>
