<?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:17:26 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-63408 — Grav API Plugin: JWT Access Token Accepted via `?token=` URL Query Parameter</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-63408</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; getgrav grav-plugin-api&lt;/p&gt;
&lt;p&gt;Grav API Plugin is a RESTful API for Grav CMS that provides full headless access to your site&amp;#39;s content.  Prior to 1.0.0-rc.16, the Grav API plugin JwtAuthenticator::extractBearerToken() accepts a JWT from the token URL query parameter on every /api/v1 route, including state-changing endpoints. Request URLs consequently expose valid access tokens through Apache, proxy, and CDN logs, browser history, and Referer headers, allowing a party with access to those records to reuse the token with the owner&amp;#39;s API privileges. This issue is fixed in version 1.0.0-rc.16.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; getgrav grav-plugin-api&lt;/p&gt;
&lt;p&gt;Grav API Plugin is a RESTful API for Grav CMS that provides full headless access to your site&amp;#39;s content.  Prior to 1.0.0-rc.16, the Grav API plugin JwtAuthenticator::extractBearerToken() accepts a JWT from the token URL query parameter on every /api/v1 route, including state-changing endpoints. Request URLs consequently expose valid access tokens through Apache, proxy, and CDN logs, browser history, and Referer headers, allowing a party with access to those records to reuse the token with the owner&amp;#39;s API privileges. This issue is fixed in version 1.0.0-rc.16.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-63408</guid>
    </item>
  </channel>
</rss>
