CVE.org (no NVD analysis yet)· CNA GitHub_M

CVE-2026-104890: Kunstmaan CMS: MediaBundle extension blacklist bypass allows authenticated administrators to upload executable PHP files leading to remote code execution

HighCVSS 7.2 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 28/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.41% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Kunstmaan KunstmaanBundlesCMS 7.3.2.

Low priority for now. Upgrade to Kunstmaan KunstmaanBundlesCMS 7.3.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published: Oct 5, 2026
Updated: Oct 7, 2026
EPSS: 0.4% · 36th percentile
CWE: CWE-434

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 28 / 40 · 7.2 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.4%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitHub_M: 7.2; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

kunstmaan bundles-cms
- < 7.3.1affected
kunstmaan media-bundle
- < 7.3.1affected
Kunstmaan KunstmaanBundlesCMS
- < 7.3.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Packagist	kunstmaan/bundles-cms	before 7.3.2	7.3.2
Packagist	kunstmaan/media-bundle	before 7.3.2	7.3.2

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Kunstmaan KunstmaanBundlesCMS	7.3.2 · description	Vendor (CNA)
Packagist:kunstmaan/bundles-cms	7.3.2	Package registry (OSV)
Packagist:kunstmaan/media-bundle	7.3.2	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.