<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-08T19:36:33.421536+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-104890</id>
    <title>fkie_cve-2026-104890</title>
    <updated>2026-10-08T19:36:33.448049+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Kunstmaan CMS is an open source content management system based on the Symfony framework. Prior to 7.3.2, src/Kunstmaan/MediaBundle/Helper/File/FileHandler.php performs the blacklisted_extensions check case-sensitively in FileHandler::getFilePath and lowercases the stored extension afterward. An authenticated backend user with media access can upload a mixed-case executable extension such as PHP that bypasses the check and is stored in the web-accessible media directory with an executable lowercase extension. The default blacklist also omits several server-executable extension types, allowing the same code-execution impact where the web server executes uploaded files. This issue is fixed in version 7.3.2.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-104890"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-p279-5wcv-45vq</id>
    <title>GHSA-p279-5wcv-45vq — Kunstmaan CMS: MediaBundle extension blacklist bypass allows authenticated administrators to upload executable PHP file…</title>
    <updated>2026-10-08T19:36:33.448138+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Packagist: kunstmaan/media-bundle, Packagist: kunstmaan/bundles-cms</p>
<p>### Summary</p>
<p>The MediaBundle blocks dangerous upload extensions with a blacklist that was matched
case-sensitively, while the stored filename was lowercased afterwards. A file uploaded
as `webshell.pHp` therefore bypassed the blacklist and was written to the web-accessible
upload directory as `webshell.php`, where the web server executed it. Any authenticated
backend user with access to the media section could obtain remote code execution.</p>
<p>### Details</p>
<p>`FileHandler::getFilePath()` rewrote blacklisted extensions to `.txt` using a
case-sensitive regex, and only then lowercased the extension when building the stored
name — so the check ran against the attacker-controlled casing and the normalisation
happened after it.</p>
<p>Two further weaknesses contributed:</p>
<p>* The default blacklist contained only `php` and `htaccess`, leaving other
  server-executable extensions (`phtml`, `php5`, `phar`, `shtml`, `cgi`, …) unblocked
  regardless of casing.
* Configured blacklist values were interpolated into the regex unescaped.</p>
<p>### Impact</p>
<p>An authenticated user with access to the admin media section can upload a file that the
web server executes as PHP. The uploaded file is reachable over HTTP without
authentication, giving arbitrary code execution as the web server user.</p>
<p>### Patches</p>
<p>Fixed in kunstmaan/media-bundle 7.3.2. The extension is now normalised before it is
checked and compared with `in_array()`; the default blacklist is expanded to the full
set of server-executable extensions; and a…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-p279-5wcv-45vq"/>
  </entry>
</feed>
