<?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>Tue, 06 Oct 2026 03:15:58 +0000</lastBuildDate>
    <item>
      <title>cnvd-2026-18153</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2026-18153</link>
      <description>cnvd-2026-18153</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2026-18153</guid>
    </item>
    <item>
      <title>EUVD-2026-275291</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-275291</link>
      <description>EUVD-2026-275291</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-275291</guid>
    </item>
    <item>
      <title>fkie_cve-2026-30944</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-30944</link>
      <description>&lt;p&gt;StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.0, the /studiocms_api/dashboard/api-tokens endpoint allows any authenticated user (at least Editor) to generate API tokens for any other user, including owner and admin accounts. The endpoint fails to validate whether the requesting user is authorized to create tokens on behalf of the target user ID, resulting in a full privilege escalation. This vulnerability is fixed in 0.4.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.0, the /studiocms_api/dashboard/api-tokens endpoint allows any authenticated user (at least Editor) to generate API tokens for any other user, including owner and admin accounts. The endpoint fails to validate whether the requesting user is authorized to create tokens on behalf of the target user ID, resulting in a full privilege escalation. This vulnerability is fixed in 0.4.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-30944</guid>
    </item>
    <item>
      <title>GHSA-667w-mmh7-mrr4 — StudioCMS has Privilege Escalation via Insecure API Token Generation</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-667w-mmh7-mrr4</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: studiocms&lt;/p&gt;
&lt;p&gt;## Summary
The /studiocms_api/dashboard/api-tokens endpoint allows any authenticated user (at least Editor) to generate API tokens for any other user, including owner and admin accounts. The endpoint fails to validate whether the requesting user is authorized to create tokens on behalf of the target user ID, resulting in a full privilege escalation.&lt;/p&gt;
&lt;p&gt;## Details
The API token generation endpoint accepts a user parameter in the request body that specifies which user the token should be created for. The server-side logic authenticates the session (via auth_session cookie) but does not verify that the authenticated user matches the target user ID nor checks if the caller has sufficient privileges to perform this action on behalf of another user.
This is a classic BOLA vulnerability: the authorization check is limited to &amp;#34;is the user logged in?&amp;#34; instead of &amp;#34;is this user authorized to perform this action on this specific resource?&amp;#34;&lt;/p&gt;
&lt;p&gt;#### Vulnerable Code
The following is the server-side handler for the POST /studiocms_api/dashboard/api-tokens endpoint:
**File:** packages/studiocms/frontend/pages/studiocms_api/dashboard/api-tokens.ts (lines 16–57)
**Version:** studiocms@0.3.0
```
POST: (ctx) =&amp;gt;
    genLogger(&amp;#39;studiocms/routes/api/dashboard/api-tokens.POST&amp;#39;)(function* () {
        const sdk = yield* SDKCore;&lt;/p&gt;
&lt;p&gt;// Check if demo mode is enabled
        if (developerConfig.demoMode !== false) {
            return apiResponseLogger(403, &amp;#39;Demo mode is enabled, this action is not al…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: studiocms&lt;/p&gt;
&lt;p&gt;## Summary
The /studiocms_api/dashboard/api-tokens endpoint allows any authenticated user (at least Editor) to generate API tokens for any other user, including owner and admin accounts. The endpoint fails to validate whether the requesting user is authorized to create tokens on behalf of the target user ID, resulting in a full privilege escalation.&lt;/p&gt;
&lt;p&gt;## Details
The API token generation endpoint accepts a user parameter in the request body that specifies which user the token should be created for. The server-side logic authenticates the session (via auth_session cookie) but does not verify that the authenticated user matches the target user ID nor checks if the caller has sufficient privileges to perform this action on behalf of another user.
This is a classic BOLA vulnerability: the authorization check is limited to &amp;#34;is the user logged in?&amp;#34; instead of &amp;#34;is this user authorized to perform this action on this specific resource?&amp;#34;&lt;/p&gt;
&lt;p&gt;#### Vulnerable Code
The following is the server-side handler for the POST /studiocms_api/dashboard/api-tokens endpoint:
**File:** packages/studiocms/frontend/pages/studiocms_api/dashboard/api-tokens.ts (lines 16–57)
**Version:** studiocms@0.3.0
```
POST: (ctx) =&amp;gt;
    genLogger(&amp;#39;studiocms/routes/api/dashboard/api-tokens.POST&amp;#39;)(function* () {
        const sdk = yield* SDKCore;&lt;/p&gt;
&lt;p&gt;// Check if demo mode is enabled
        if (developerConfig.demoMode !== false) {
            return apiResponseLogger(403, &amp;#39;Demo mode is enabled, this action is not al…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-667w-mmh7-mrr4</guid>
    </item>
  </channel>
</rss>
