<?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://cve.radiocsirt.org</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, 10 Oct 2026 15:23:05 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-318007</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-318007</link>
      <description>EUVD-2026-318007</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-318007</guid>
    </item>
    <item>
      <title>fkie_cve-2026-42844</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-42844</link>
      <description>&lt;p&gt;Grav is a file-based Web platform. In Grav 2.0.0-beta.2, a low-privileged authenticated API user with api.media.write can abuse /api/v1/blueprint-upload to write an arbitrary YAML file into user/accounts/, then log in as the newly created account with api.super privileges. This results in full administrative compromise of the Grav API. This vulnerability is fixed in API 1.0.0-beta.17.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Grav is a file-based Web platform. In Grav 2.0.0-beta.2, a low-privileged authenticated API user with api.media.write can abuse /api/v1/blueprint-upload to write an arbitrary YAML file into user/accounts/, then log in as the newly created account with api.super privileges. This results in full administrative compromise of the Grav API. This vulnerability is fixed in API 1.0.0-beta.17.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-42844</guid>
    </item>
    <item>
      <title>GHSA-6xx2-m8wv-756h — Low-privileged Grav API users can create super-admin accounts via blueprint-upload</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6xx2-m8wv-756h</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: getgrav/grav&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;In Grav `2.0.0-beta.2`, a low-privileged authenticated API user with `api.media.write` can abuse `/api/v1/blueprint-upload` to write an arbitrary YAML file into `user/accounts/`, then log in as the newly created account with `api.super` privileges.&lt;/p&gt;
&lt;p&gt;This results in full administrative compromise of the Grav API.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;The vulnerability is located in the API plugin&amp;#39;s blueprint upload flow:&lt;/p&gt;
&lt;p&gt;- `user/plugins/api/classes/Api/ApiRouter.php:261`
- `user/plugins/api/classes/Api/Controllers/BlueprintUploadController.php:32-45`
- `user/plugins/api/classes/Api/Controllers/BlueprintUploadController.php:102-114`
- `user/plugins/api/classes/Api/Controllers/BlueprintUploadController.php:271-308`
- `user/plugins/api/classes/Api/Controllers/BlueprintUploadController.php:407-417`
- `user/plugins/api/classes/Api/Controllers/AuthController.php:41-55`&lt;/p&gt;
&lt;p&gt;The issue exists because `/api/v1/blueprint-upload` accepts caller-controlled `destination` and `scope` values and uses them to resolve the final filesystem write target.&lt;/p&gt;
&lt;p&gt;When the request uses:&lt;/p&gt;
&lt;p&gt;- `destination=self@:`
- `scope=users/anything`&lt;/p&gt;
&lt;p&gt;The server resolves the write target to the shared account directory:&lt;/p&gt;
&lt;p&gt;```text
user/accounts/
```&lt;/p&gt;
&lt;p&gt;The upload handler then writes the supplied file directly into that directory and does not block YAML account files. Because Grav accepts account YAML files and supports a plaintext `password:` field on first login, an attacker can create a fully functional administrator account with `api.s…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: getgrav/grav&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;In Grav `2.0.0-beta.2`, a low-privileged authenticated API user with `api.media.write` can abuse `/api/v1/blueprint-upload` to write an arbitrary YAML file into `user/accounts/`, then log in as the newly created account with `api.super` privileges.&lt;/p&gt;
&lt;p&gt;This results in full administrative compromise of the Grav API.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;The vulnerability is located in the API plugin&amp;#39;s blueprint upload flow:&lt;/p&gt;
&lt;p&gt;- `user/plugins/api/classes/Api/ApiRouter.php:261`
- `user/plugins/api/classes/Api/Controllers/BlueprintUploadController.php:32-45`
- `user/plugins/api/classes/Api/Controllers/BlueprintUploadController.php:102-114`
- `user/plugins/api/classes/Api/Controllers/BlueprintUploadController.php:271-308`
- `user/plugins/api/classes/Api/Controllers/BlueprintUploadController.php:407-417`
- `user/plugins/api/classes/Api/Controllers/AuthController.php:41-55`&lt;/p&gt;
&lt;p&gt;The issue exists because `/api/v1/blueprint-upload` accepts caller-controlled `destination` and `scope` values and uses them to resolve the final filesystem write target.&lt;/p&gt;
&lt;p&gt;When the request uses:&lt;/p&gt;
&lt;p&gt;- `destination=self@:`
- `scope=users/anything`&lt;/p&gt;
&lt;p&gt;The server resolves the write target to the shared account directory:&lt;/p&gt;
&lt;p&gt;```text
user/accounts/
```&lt;/p&gt;
&lt;p&gt;The upload handler then writes the supplied file directly into that directory and does not block YAML account files. Because Grav accepts account YAML files and supports a plaintext `password:` field on first login, an attacker can create a fully functional administrator account with `api.s…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6xx2-m8wv-756h</guid>
    </item>
  </channel>
</rss>
