<?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>Thu, 12 Nov 2026 11:44:40 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-119615</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-119615</link>
      <description>&lt;p&gt;The Reset Database plugin for WordPress is vulnerable to privilege escalation in versions up to, and including, 1.1.3. This is due to the process_reset() function being registered on admin_init with no capability check, a computed-but-unused nonce, a gating condition that passes whenever no WordPress administrator literally named &amp;#39;admin&amp;#39; exists (the default on modern installs), and an identity test that verifies the ATTACKER&amp;#39;S OWN password rather than an administrator&amp;#39;s. This makes it possible for authenticated attackers, with subscriber-level access and above, to drop every prefixed database table, re-run wp_install() with their own credentials — making the attacker the sole site administrator — authenticate as that administrator via wp_set_auth_cookie(), and delete the uploads directory.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Reset Database plugin for WordPress is vulnerable to privilege escalation in versions up to, and including, 1.1.3. This is due to the process_reset() function being registered on admin_init with no capability check, a computed-but-unused nonce, a gating condition that passes whenever no WordPress administrator literally named &amp;#39;admin&amp;#39; exists (the default on modern installs), and an identity test that verifies the ATTACKER&amp;#39;S OWN password rather than an administrator&amp;#39;s. This makes it possible for authenticated attackers, with subscriber-level access and above, to drop every prefixed database table, re-run wp_install() with their own credentials — making the attacker the sole site administrator — authenticate as that administrator via wp_set_auth_cookie(), and delete the uploads directory.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-119615</guid>
    </item>
    <item>
      <title>GHSA-qrxx-fg3m-g5wv</title>
      <link>https://db.gcve.eu/vuln/ghsa-qrxx-fg3m-g5wv</link>
      <description>&lt;p&gt;The Reset Database plugin for WordPress is vulnerable to privilege escalation in versions up to, and including, 1.1.3. This is due to the process_reset() function being registered on admin_init with no capability check, a computed-but-unused nonce, a gating condition that passes whenever no WordPress administrator literally named &amp;#39;admin&amp;#39; exists (the default on modern installs), and an identity test that verifies the ATTACKER&amp;#39;S OWN password rather than an administrator&amp;#39;s. This makes it possible for authenticated attackers, with subscriber-level access and above, to drop every prefixed database table, re-run wp_install() with their own credentials — making the attacker the sole site administrator — authenticate as that administrator via wp_set_auth_cookie(), and delete the uploads directory.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Reset Database plugin for WordPress is vulnerable to privilege escalation in versions up to, and including, 1.1.3. This is due to the process_reset() function being registered on admin_init with no capability check, a computed-but-unused nonce, a gating condition that passes whenever no WordPress administrator literally named &amp;#39;admin&amp;#39; exists (the default on modern installs), and an identity test that verifies the ATTACKER&amp;#39;S OWN password rather than an administrator&amp;#39;s. This makes it possible for authenticated attackers, with subscriber-level access and above, to drop every prefixed database table, re-run wp_install() with their own credentials — making the attacker the sole site administrator — authenticate as that administrator via wp_set_auth_cookie(), and delete the uploads directory.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-qrxx-fg3m-g5wv</guid>
    </item>
  </channel>
</rss>
