<?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>Fri, 20 Nov 2026 08:47:39 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-84987</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-84987</link>
      <description>&lt;p&gt;code16 Sharp is a Laravel-based framework for building content-management and administrative interfaces. Prior to 9.23.0, an authenticated attacker can call the autocomplete API with a request endpoint that contains the configured remote endpoint only as a substring. The endpoint validation uses an unanchored regular expression, so a different internal route can satisfy the check and be invoked server-side through the autocomplete request. The vulnerable path uses SharpFormAutocompleteRemoteField::setRemoteEndpoint(); applications using SharpFormAutocompleteRemoteField::setRemoteCallback() are not affected by this endpoint-selection flaw. This issue is fixed in version 9.23.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;code16 Sharp is a Laravel-based framework for building content-management and administrative interfaces. Prior to 9.23.0, an authenticated attacker can call the autocomplete API with a request endpoint that contains the configured remote endpoint only as a substring. The endpoint validation uses an unanchored regular expression, so a different internal route can satisfy the check and be invoked server-side through the autocomplete request. The vulnerable path uses SharpFormAutocompleteRemoteField::setRemoteEndpoint(); applications using SharpFormAutocompleteRemoteField::setRemoteCallback() are not affected by this endpoint-selection flaw. This issue is fixed in version 9.23.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-84987</guid>
    </item>
    <item>
      <title>GHSA-g6f8-c3x9-jv7f — code16/sharp: Server-side request forgery through an unanchored autocomplete endpoint check</title>
      <link>https://db.gcve.eu/vuln/ghsa-g6f8-c3x9-jv7f</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: code16/sharp&lt;/p&gt;
&lt;p&gt;### Impact
An authenticated attacker can call the Autocomplete API with the configured endpoint as a substring to request another server-side route.&lt;/p&gt;
&lt;p&gt;### Patches
The problem has been patched in 9.23.0 and pre-release version 10.0.0-beta.4. The regex verifying the endpoint has been anchored to forbid substring injection.&lt;/p&gt;
&lt;p&gt;### Workarounds
Use `SharpFormAutocompleteRemoteField::setRemoteCallback()` instead of `SharpFormAutocompleteRemoteField::setRemoteEndpoint()`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: code16/sharp&lt;/p&gt;
&lt;p&gt;### Impact
An authenticated attacker can call the Autocomplete API with the configured endpoint as a substring to request another server-side route.&lt;/p&gt;
&lt;p&gt;### Patches
The problem has been patched in 9.23.0 and pre-release version 10.0.0-beta.4. The regex verifying the endpoint has been anchored to forbid substring injection.&lt;/p&gt;
&lt;p&gt;### Workarounds
Use `SharpFormAutocompleteRemoteField::setRemoteCallback()` instead of `SharpFormAutocompleteRemoteField::setRemoteEndpoint()`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-g6f8-c3x9-jv7f</guid>
    </item>
  </channel>
</rss>
