# Pimcore CSRF Vulnerability

Advisory record · `GHSA-gmff-vcv6-mmfr`

- **Identifiers:** `GHSA-gmff-vcv6-mmfr` · `CVE-2018-14057` · `PKSA-244f-9rfv-862d`
- **State:** Confirmed
- **Severity:** CVSS 8.8 High
- **Critical:** No
- **Weakness (CWE):** [CWE-352](https://cwe.mitre.org/data/definitions/352.html)
- **Tags:** [Cross-site request forgery (CSRF)](https://agentprime.io/advisories/tag/csrf.md)
- **Published:** 14 May 2022
- **Updated:** 18 Feb 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 14 May 2022, 02:36 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `pimcore/pimcore` (Packagist): affected `<5.3.0`; fixed in `5.3.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Pimcore versions before 5.3.0 are vulnerable to cross-site request forgery. The anti-CSRF token in the X-pimcore-csrf-token header is only validated in the Settings > Users / Roles function, so a remote attacker can lure a logged-in user into sending requests that other parts of the application accept without the token. Upgrade pimcore/pimcore to version 5.3.0 or later. The source gives few details on which other functions are affected.

Written 4 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.8 High, CVSS 3.0: `CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.033, the 88th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:30 UTC: First seen by agentprime
- 31 Oct 2026, 14:30 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-gmff-vcv6-mmfr)

## Sources

- [GitHub Advisory Database: GHSA-gmff-vcv6-mmfr](https://github.com/advisories/GHSA-gmff-vcv6-mmfr)
- [OSV: GHSA-gmff-vcv6-mmfr](https://osv.dev/vulnerability/GHSA-gmff-vcv6-mmfr)
- <https://nvd.nist.gov/vuln/detail/CVE-2018-14057>
- <https://www.exploit-db.com/exploits/45208>
- <https://www.sec-consult.com/en/blog/advisories/sql-injection-xss-csrf-vulnerabilities-in-pimcore-software>
- <http://packetstormsecurity.com/files/148954/Pimcore-5.2.3-CSRF-Cross-Site-Scripting-SQL-Injection.html>
- <http://seclists.org/fulldisclosure/2018/Aug/13>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-gmff-vcv6-mmfr>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-gmff-vcv6-mmfr/>. Everything for agents: <https://agentprime.io/llms.txt>.
