<?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-21T10:08:47.103382+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-121150</id>
    <title>CVE-2026-121150 — UpdraftPlus (Free &amp; Pro) - Subscriber+ Privilege Escalation via Backup Restore Comment Discard SQLi</title>
    <updated>2026-11-21T10:08:47.104674+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Unknown UpdraftPlus: WP Backup &amp; Migration Plugin</p>
<p>The UpdraftPlus: WP Backup &amp; Migration Plugin WordPress plugin before 2.26.16.26, UpdraftPlus: WP Backup &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.</p>
<p>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's maximum packet size.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-121150"/>
  </entry>
</feed>
