<?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, 07 Nov 2026 19:35:22 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-84728</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-84728</link>
      <description>&lt;p&gt;Incorrect Authorization in Apache OFBiz 
24.09 before 24.09.08 on all platforms, when documented multitenancy is 
enabled, allows a remote authenticated attacker holding only a valid 
low-privilege account in one tenant to read and write data belonging to a
 different tenant, by submitting their own tenant&amp;#39;s userTenantId 
alongside their own credentials to the normal Party Manager login 
against a hostname mapped to a different tenant: ContextFilter resolves 
the tenant from the hostname via TenantDomainName, but LoginWorker gives
 priority to the conflicting userTenantId request parameter and 
authenticates against the attacker&amp;#39;s own tenant, so a subsequent 
ordinary request to the same hostname combines the hostname-mapped 
tenant&amp;#39;s Entity Engine delegator with the attacker&amp;#39;s tenant&amp;#39;s session 
dispatcher, security object, and identity, letting the permission check 
run against the attacker&amp;#39;s own tenant while the resulting read or write 
is performed against the hostname-mapped tenant&amp;#39;s data. Users are 
recommended to upgrade to version 24.09.08, which fixes this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Incorrect Authorization in Apache OFBiz 
24.09 before 24.09.08 on all platforms, when documented multitenancy is 
enabled, allows a remote authenticated attacker holding only a valid 
low-privilege account in one tenant to read and write data belonging to a
 different tenant, by submitting their own tenant&amp;#39;s userTenantId 
alongside their own credentials to the normal Party Manager login 
against a hostname mapped to a different tenant: ContextFilter resolves 
the tenant from the hostname via TenantDomainName, but LoginWorker gives
 priority to the conflicting userTenantId request parameter and 
authenticates against the attacker&amp;#39;s own tenant, so a subsequent 
ordinary request to the same hostname combines the hostname-mapped 
tenant&amp;#39;s Entity Engine delegator with the attacker&amp;#39;s tenant&amp;#39;s session 
dispatcher, security object, and identity, letting the permission check 
run against the attacker&amp;#39;s own tenant while the resulting read or write 
is performed against the hostname-mapped tenant&amp;#39;s data. Users are 
recommended to upgrade to version 24.09.08, which fixes this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-84728</guid>
    </item>
    <item>
      <title>GHSA-xqg5-g7cj-f6x6</title>
      <link>https://db.gcve.eu/vuln/ghsa-xqg5-g7cj-f6x6</link>
      <description>&lt;p&gt;Incorrect Authorization in Apache OFBiz 
24.09 before 24.09.08 on all platforms, when documented multitenancy is 
enabled, allows a remote authenticated attacker holding only a valid 
low-privilege account in one tenant to read and write data belonging to a
 different tenant, by submitting their own tenant&amp;#39;s userTenantId 
alongside their own credentials to the normal Party Manager login 
against a hostname mapped to a different tenant: ContextFilter resolves 
the tenant from the hostname via TenantDomainName, but LoginWorker gives
 priority to the conflicting userTenantId request parameter and 
authenticates against the attacker&amp;#39;s own tenant, so a subsequent 
ordinary request to the same hostname combines the hostname-mapped 
tenant&amp;#39;s Entity Engine delegator with the attacker&amp;#39;s tenant&amp;#39;s session 
dispatcher, security object, and identity, letting the permission check 
run against the attacker&amp;#39;s own tenant while the resulting read or write 
is performed against the hostname-mapped tenant&amp;#39;s data. Users are 
recommended to upgrade to version 24.09.08, which fixes this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Incorrect Authorization in Apache OFBiz 
24.09 before 24.09.08 on all platforms, when documented multitenancy is 
enabled, allows a remote authenticated attacker holding only a valid 
low-privilege account in one tenant to read and write data belonging to a
 different tenant, by submitting their own tenant&amp;#39;s userTenantId 
alongside their own credentials to the normal Party Manager login 
against a hostname mapped to a different tenant: ContextFilter resolves 
the tenant from the hostname via TenantDomainName, but LoginWorker gives
 priority to the conflicting userTenantId request parameter and 
authenticates against the attacker&amp;#39;s own tenant, so a subsequent 
ordinary request to the same hostname combines the hostname-mapped 
tenant&amp;#39;s Entity Engine delegator with the attacker&amp;#39;s tenant&amp;#39;s session 
dispatcher, security object, and identity, letting the permission check 
run against the attacker&amp;#39;s own tenant while the resulting read or write 
is performed against the hostname-mapped tenant&amp;#39;s data. Users are 
recommended to upgrade to version 24.09.08, which fixes this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-xqg5-g7cj-f6x6</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4357 — Apache OFBiz: Mehrere Schwachstellen</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4357</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Apache OFBiz ausnutzen, um Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten offenzulegen, Bestell- und Zahlungsdaten zu manipulieren oder einen DoS auszulösen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Apache OFBiz ausnutzen, um Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten offenzulegen, Bestell- und Zahlungsdaten zu manipulieren oder einen DoS auszulösen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4357</guid>
    </item>
  </channel>
</rss>
