Vulnerabilities · 2019 · Pimcore
CVE-2019-16318
Pimcore vulnerability
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.
Affected products
Pimcore. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Pimcore runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/pimcore/pimcore/commit/732f1647cc6e0a29b5b1f5d904b4d726b5e9455f · Patch
- snyk.io/vuln/SNYK-PHP-PIMCOREPIMCORE-451598 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2019-16318
- github.com/advisories/GHSA-cxj7-4jpj-2q38
- nvd.nist.gov/vuln/detail/CVE-2019-16318
- cve.org/CVERecord?id=CVE-2019-16318
More vulnerabilities in Pimcore products
CVE-2026-23496CVE-2026-23495CVE-2026-23494CVE-2026-23493CVE-2026-23492CVE-2025-30166CVE-2025-27617CVE-2025-24980All 153
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.