<?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>Mon, 12 Oct 2026 07:42:10 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-277920</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-277920</link>
      <description>EUVD-2026-277920</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-277920</guid>
    </item>
    <item>
      <title>fkie_cve-2026-33687</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-33687</link>
      <description>&lt;p&gt;Sharp is a content management framework built for Laravel as a package. Versions prior to 9.20.0 contain a vulnerability in the file upload endpoint that allows authenticated users to bypass all file type restrictions. The upload endpoint within the `ApiFormUploadController` accepts a client-controlled `validation_rule` parameter. This parameter is directly passed into the Laravel validator without sufficient server-side enforcement. By intercepting the request and sending `validation_rule[]=file`, an attacker can completely bypass all MIME type and file extension restrictions. This issue has been addressed in version 9.20.0 by removing the client-controlled validation rules and strictly defining upload rules server-side. As a workaround, ensure that the storage disk used for Sharp uploads is strictly private. Under default configurations, an attacker cannot directly execute uploaded PHP files unless a public disk configuration is explicitly used.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Sharp is a content management framework built for Laravel as a package. Versions prior to 9.20.0 contain a vulnerability in the file upload endpoint that allows authenticated users to bypass all file type restrictions. The upload endpoint within the `ApiFormUploadController` accepts a client-controlled `validation_rule` parameter. This parameter is directly passed into the Laravel validator without sufficient server-side enforcement. By intercepting the request and sending `validation_rule[]=file`, an attacker can completely bypass all MIME type and file extension restrictions. This issue has been addressed in version 9.20.0 by removing the client-controlled validation rules and strictly defining upload rules server-side. As a workaround, ensure that the storage disk used for Sharp uploads is strictly private. Under default configurations, an attacker cannot directly execute uploaded PHP files unless a public disk configuration is explicitly used.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-33687</guid>
    </item>
    <item>
      <title>GHSA-fr76-5637-w3g9 — Sharp has Unrestricted File Upload via Client-Controlled Validation Rules</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-fr76-5637-w3g9</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: code16/sharp&lt;/p&gt;
&lt;p&gt;### Summary 
The `code16/sharp` Laravel admin panel package contains a vulnerability in its file upload endpoint that allows authenticated users to bypass all file type restrictions.&lt;/p&gt;
&lt;p&gt;### Details
The upload endpoint within the `ApiFormUploadController` accepts a client-controlled `validation_rule` parameter. This parameter is directly passed into the Laravel validator without sufficient server-side enforcement. By intercepting the request and sending `validation_rule[]=file`, an attacker can completely bypass all MIME type and file extension restrictions. The vulnerable code is located in `src/Http/Controllers/Api/ApiFormUploadController.php` at line 24.&lt;/p&gt;
&lt;p&gt;### Impact
This vulnerability leads to several critical security risks:&lt;/p&gt;
&lt;p&gt;Attackers can upload arbitrary files, including PHP webshells, to the server. For more details on the package, visit: https://github.com/code16/sharp&lt;/p&gt;
&lt;p&gt;MIME type and extension validation can be bypassed entirely via client-controlled rules. Review the CWE definition here: https://cwe.mitre.org/data/definitions/434.html&lt;/p&gt;
&lt;p&gt;If the storage disk is configured to be publicly accessible, this can lead to Remote Code Execution (RCE). See the vendor repository: https://github.com/code16/sharp&lt;/p&gt;
&lt;p&gt;(Note: Under default configurations, executing uploaded PHP files directly is not possible unless a public disk configuration is in place.)&lt;/p&gt;
&lt;p&gt;### Patches
This issue has been addressed by removing the client-controlled validation rules and strictly defining upload rules serve…&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;### Summary 
The `code16/sharp` Laravel admin panel package contains a vulnerability in its file upload endpoint that allows authenticated users to bypass all file type restrictions.&lt;/p&gt;
&lt;p&gt;### Details
The upload endpoint within the `ApiFormUploadController` accepts a client-controlled `validation_rule` parameter. This parameter is directly passed into the Laravel validator without sufficient server-side enforcement. By intercepting the request and sending `validation_rule[]=file`, an attacker can completely bypass all MIME type and file extension restrictions. The vulnerable code is located in `src/Http/Controllers/Api/ApiFormUploadController.php` at line 24.&lt;/p&gt;
&lt;p&gt;### Impact
This vulnerability leads to several critical security risks:&lt;/p&gt;
&lt;p&gt;Attackers can upload arbitrary files, including PHP webshells, to the server. For more details on the package, visit: https://github.com/code16/sharp&lt;/p&gt;
&lt;p&gt;MIME type and extension validation can be bypassed entirely via client-controlled rules. Review the CWE definition here: https://cwe.mitre.org/data/definitions/434.html&lt;/p&gt;
&lt;p&gt;If the storage disk is configured to be publicly accessible, this can lead to Remote Code Execution (RCE). See the vendor repository: https://github.com/code16/sharp&lt;/p&gt;
&lt;p&gt;(Note: Under default configurations, executing uploaded PHP files directly is not possible unless a public disk configuration is in place.)&lt;/p&gt;
&lt;p&gt;### Patches
This issue has been addressed by removing the client-controlled validation rules and strictly defining upload rules serve…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-fr76-5637-w3g9</guid>
    </item>
  </channel>
</rss>
