# Pimcore Discloses Usernames In Use

Advisory record · `GHSA-8889-9g3f-73rj`

- **Identifiers:** `GHSA-8889-9g3f-73rj` · `CVE-2019-18986` · `PKSA-54j1-2ssn-spm4`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-307](https://cwe.mitre.org/data/definitions/307.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 24 May 2022
- **Updated:** 16 Feb 2024
- **Reviewed by a person:** No

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

## Affected packages

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

## Machine-written summary

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

> Pimcore versions before 6.2.2 are vulnerable. An attacker can use the "forgot password" function to guess valid usernames, because it returns different messages for existing and non-existing users. Upgrade pimcore/pimcore to 6.2.2 or later.

Written 5 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

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

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

## Timeline

- 31 Oct 2026, 14:32 UTC: First seen by agentprime
- 31 Oct 2026, 14:32 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-8889-9g3f-73rj)

## Sources

- [GitHub Advisory Database: GHSA-8889-9g3f-73rj](https://github.com/advisories/GHSA-8889-9g3f-73rj)
- [OSV: GHSA-8889-9g3f-73rj](https://osv.dev/vulnerability/GHSA-8889-9g3f-73rj)
- <https://nvd.nist.gov/vuln/detail/CVE-2019-18986>
- <https://github.com/pimcore/pimcore/commit/4a7bba5c3f818852cbbd29fa124f7fb09a207185>
- <https://github.com/pimcore/pimcore>
- <https://github.com/pimcore/pimcore/compare/v6.2.1...v6.2.2>

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-8889-9g3f-73rj>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-8889-9g3f-73rj/>. Everything for agents: <https://agentprime.io/llms.txt>.
