<?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>Fri, 30 Oct 2026 17:34:19 +0000</lastBuildDate>
    <item>
      <title>DRUPAL-CONTRIB-2026-252</title>
      <link>https://db.gcve.eu/vuln/drupal-contrib-2026-252</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist:https://packages.drupal.org/8: drupal/rabbit_hole&lt;/p&gt;
&lt;p&gt;Rabbit Hole lets site builders control what happens when an entity&amp;#39;s page is viewed: show it, return an access denied or not found response, or redirect the visitor to another URL.&lt;/p&gt;
&lt;p&gt;The module has two vulnerabilities.&lt;/p&gt;
&lt;p&gt;Rabbit Hole behavior can be skipped with a specific query parameter. In these cases, an affected entity made Rabbit Hole treat the request as an error page and do nothing. An anonymous visitor could view content a site had configured to return an access denied or not found response, or avoid a configured redirect.&lt;/p&gt;
&lt;p&gt;The per-entity settings are stored in fields that the module adds to supported entity types. The module only checks the &amp;#34;Administer Rabbit Hole settings for `&amp;lt;entity type&amp;gt;`&amp;#34; permission when it decides whether to show those settings on the entity edit form. The fields themselves carry no access control, so Drupal&amp;#39;s default field access applies and anyone who can edit the entity can also edit these fields.&lt;/p&gt;
&lt;p&gt;The first vulnerability affects every site that relies on Rabbit Hole to deny access to or hide entities. The second is mitigated by the fact that an attacker must have a role with permission to edit the affected entities, and the site must expose a write path that bypasses the entity form, such as JSON:API with writes enabled, REST, or Views Bulk Operations.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist:https://packages.drupal.org/8: drupal/rabbit_hole&lt;/p&gt;
&lt;p&gt;Rabbit Hole lets site builders control what happens when an entity&amp;#39;s page is viewed: show it, return an access denied or not found response, or redirect the visitor to another URL.&lt;/p&gt;
&lt;p&gt;The module has two vulnerabilities.&lt;/p&gt;
&lt;p&gt;Rabbit Hole behavior can be skipped with a specific query parameter. In these cases, an affected entity made Rabbit Hole treat the request as an error page and do nothing. An anonymous visitor could view content a site had configured to return an access denied or not found response, or avoid a configured redirect.&lt;/p&gt;
&lt;p&gt;The per-entity settings are stored in fields that the module adds to supported entity types. The module only checks the &amp;#34;Administer Rabbit Hole settings for `&amp;lt;entity type&amp;gt;`&amp;#34; permission when it decides whether to show those settings on the entity edit form. The fields themselves carry no access control, so Drupal&amp;#39;s default field access applies and anyone who can edit the entity can also edit these fields.&lt;/p&gt;
&lt;p&gt;The first vulnerability affects every site that relies on Rabbit Hole to deny access to or hide entities. The second is mitigated by the fact that an attacker must have a role with permission to edit the affected entities, and the site must expose a write path that bypasses the entity form, such as JSON:API with writes enabled, REST, or Views Bulk Operations.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/drupal-contrib-2026-252</guid>
    </item>
    <item>
      <title>fkie_cve-2026-114571</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-114571</link>
      <description>&lt;p&gt;Incorrect Authorization vulnerability in Drupal Rabbit Hole allows Forceful Browsing. This issue affects Rabbit Hole versions: from 0.0.0 to 1.3.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Incorrect Authorization vulnerability in Drupal Rabbit Hole allows Forceful Browsing. This issue affects Rabbit Hole versions: from 0.0.0 to 1.3.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-114571</guid>
    </item>
    <item>
      <title>GHSA-789f-rg5c-h6q2</title>
      <link>https://db.gcve.eu/vuln/ghsa-789f-rg5c-h6q2</link>
      <description>&lt;p&gt;Incorrect Authorization vulnerability in Drupal Rabbit Hole allows Forceful Browsing. This issue affects Rabbit Hole versions: from 0.0.0 to 1.3.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Incorrect Authorization vulnerability in Drupal Rabbit Hole allows Forceful Browsing. This issue affects Rabbit Hole versions: from 0.0.0 to 1.3.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-789f-rg5c-h6q2</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4230 — Drupal Erweiterungen: Mehrere Schwachstellen</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4230</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Drupal ausnutzen, um erweiterte Berechtigungen zu erlangen und Benutzerkonten zu übernehmen, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen, Daten zu manipulieren, Cross-Site-Scripting-Angriffe durchzuführen und nicht näher spezifizierte Auswirkungen zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Drupal ausnutzen, um erweiterte Berechtigungen zu erlangen und Benutzerkonten zu übernehmen, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen, Daten zu manipulieren, Cross-Site-Scripting-Angriffe durchzuführen und nicht näher spezifizierte Auswirkungen zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4230</guid>
    </item>
  </channel>
</rss>
