CVE-2019-16318 Pimcore Unrestricted Upload of File with Dangerous Type
Attackers with limited privileges can bypass file extension restrictions by using long filenames, potentially uploading malicious PHP files for code execution.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2019-16318?
CVE-2019-16318 is a high-severity vulnerability in Pimcore Pimcore, published on 14 Sep 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
In Pimcore before 5.7.1, an attacker with limited privileges can bypass file-extension restrictions via a 256-character filename, as demonstrated by the failure of automatic renaming of .php to .php.txt for long filenames, a different vulnerability than CVE-2019-10867 and CVE-2019-16317.
Weakness: CWE-434
Which versions are affected by CVE-2019-16318?
2 open source packages ship an affected version, including pimcore/pimcore. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
pimcore/pimcore Packagist | All versions | 5.7.1 |
pimcore/pimcore Packagist | All versions | 5.7.1 |
Products include Pimcore Pimcore.
How do I fix CVE-2019-16318?
Upgrade pimcore/pimcore to 5.7.1 or later.
Is CVE-2019-16318 being exploited?
There is no known exploitation of CVE-2019-16318 in the wild and no public exploit code.
Other vulnerabilities in Pimcore Pimcore
- CVE-2022-39365 RCE vulnerability in Pimcore/Mail & Dynamic Text Layout
- CVE-2019-18981 Pimcore Access Control Issues
- CVE-2019-18985 Pimcore 2FA Vulnerable to Brute Forcing
- CVE-2026-23492 Pimcore has a Blind SQL Injection in Admin Search Find API due to an incomplete fix for CVE-2023-30848
- CVE-2023-47637 SQL Injection in Admin Grid Filter API in Pimcore
Sources
Also known as GHSA-cxj7-4jpj-2q38, SNYK-PHP-PIMCOREPIMCORE-451598.