CVE-2019-16318

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.

Category

8.8
CVSS
Severity: High
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.01%
Third-Party Advisory snyk.io
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://github.com/pimcore/pimcore/commit/732f1647cc6e0a29b5b1f5d904b4d726b5e9455f patch
https://snyk.io/vuln/SNYK-PHP-PIMCOREPIMCORE-451598 third party advisory

Frequently Asked Questions

What is the severity of CVE-2019-16318?
CVE-2019-16318 has been scored as a high severity vulnerability.
How to fix CVE-2019-16318?
To fix CVE-2019-16318, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2019-16318 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2019-16318 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.