Ibexa Kernel's files with blacklisted extensions can be still saved to drafts
Impact
File validation can be configured to reject certain files by file type. When this happens, validation fails, and the content can't be published. However, the file can be saved when saving the content draft. This means unwanted files can be present in storage, even if they are not easily accessible due to the content not being published. The fix ensures these unwanted file types are never stored. An attacker would need to have existing access to create content with a file field type to exploit this.
Patches
See "Patched versions". Commit: https://github.com/ibexa/core/commit/7e472317f7c75f45f72f74c38406952d8bea0de1
References
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Composer package | ibexa/core | >= 4.5.0, < 4.5.6, >= 4.6.0, < 4.6.2 | 4.5.6, 4.6.2 |
References
- Weakness (CWE)
CWE-434- Platform
- Composer
- Package
ibexa/core- Disclosed
- 20.03.2024
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-9j39-4686-m3c4 - CC BY 4.0
Vulnerability history: ibexa/core
All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 5
- First → latest
- 04.2022 03.2024
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Critical 3
- Medium 1
- Low 1
Disclosures per year
- 2022: 3
- 2023: 1
- 2024: 1
- 2025: 0
- 2026: 0
-
Ibexa Kernel's files with blacklisted extensions can be still saved to drafts this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.