<?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>Tue, 06 Oct 2026 06:21:05 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-75832</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-75832</link>
      <description>&lt;p&gt;The Grav API plugin (getgrav/grav-plugin-api, bundled with Grav 2.0) before version 1.0.14 (fixed in 1.0.15) contains a missing authorization vulnerability in BlueprintPathResolver::resolveUserScope(). The method gates the users/&amp;lt;name&amp;gt; scope on the account&amp;#39;s raw super-admin ACL flag (access.api.super) instead of validating the presented API key&amp;#39;s actual scope. An attacker holding an API key scoped only to api.media.write minted on a super-admin account can bypass the authorization check and, via POST /blueprint-upload or GET /blueprint-files, write a file into another user&amp;#39;s scope (in the shared user/accounts/ directory, constrained to image extensions by assertSafeExtension()) and browse that scope&amp;#39;s file listing, despite the key not being granted api.users.write.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Grav API plugin (getgrav/grav-plugin-api, bundled with Grav 2.0) before version 1.0.14 (fixed in 1.0.15) contains a missing authorization vulnerability in BlueprintPathResolver::resolveUserScope(). The method gates the users/&amp;lt;name&amp;gt; scope on the account&amp;#39;s raw super-admin ACL flag (access.api.super) instead of validating the presented API key&amp;#39;s actual scope. An attacker holding an API key scoped only to api.media.write minted on a super-admin account can bypass the authorization check and, via POST /blueprint-upload or GET /blueprint-files, write a file into another user&amp;#39;s scope (in the shared user/accounts/ directory, constrained to image extensions by assertSafeExtension()) and browse that scope&amp;#39;s file listing, despite the key not being granted api.users.write.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-75832</guid>
    </item>
    <item>
      <title>GHSA-xgr3-7x2w-f8vc</title>
      <link>https://db.gcve.eu/vuln/ghsa-xgr3-7x2w-f8vc</link>
      <description>&lt;p&gt;The Grav API plugin (getgrav/grav-plugin-api, bundled with Grav 2.0) before version 1.0.14 (fixed in 1.0.15) contains a missing authorization vulnerability in BlueprintPathResolver::resolveUserScope(). The method gates the users/&amp;lt;name&amp;gt; scope on the account&amp;#39;s raw super-admin ACL flag (access.api.super) instead of validating the presented API key&amp;#39;s actual scope. An attacker holding an API key scoped only to api.media.write minted on a super-admin account can bypass the authorization check and, via POST /blueprint-upload or GET /blueprint-files, write a file into another user&amp;#39;s scope (in the shared user/accounts/ directory, constrained to image extensions by assertSafeExtension()) and browse that scope&amp;#39;s file listing, despite the key not being granted api.users.write.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Grav API plugin (getgrav/grav-plugin-api, bundled with Grav 2.0) before version 1.0.14 (fixed in 1.0.15) contains a missing authorization vulnerability in BlueprintPathResolver::resolveUserScope(). The method gates the users/&amp;lt;name&amp;gt; scope on the account&amp;#39;s raw super-admin ACL flag (access.api.super) instead of validating the presented API key&amp;#39;s actual scope. An attacker holding an API key scoped only to api.media.write minted on a super-admin account can bypass the authorization check and, via POST /blueprint-upload or GET /blueprint-files, write a file into another user&amp;#39;s scope (in the shared user/accounts/ directory, constrained to image extensions by assertSafeExtension()) and browse that scope&amp;#39;s file listing, despite the key not being granted api.users.write.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-xgr3-7x2w-f8vc</guid>
    </item>
  </channel>
</rss>
