CVE-2021-39189

CVE-2021-39189 is a medium-severity security vulnerability in pimcore/pimcore (composer), affecting versions < 10.1.3. It is fixed in 10.1.3.

Summary

Workarounds

Apply https://github.com/pimcore/pimcore/pull/10223.patch manually.

Impact

It is possible to enumerate usernames via the forgot password functionality

CVE-2021-39189 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (10.1.3); upgrading removes the vulnerable code path.

Affected versions

pimcore/pimcore (< 10.1.3)

Security releases

pimcore/pimcore → 10.1.3 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Update to version 10.1.3 or apply this patch manually: https://github.com/pimcore/pimcore/pull/10223.patch

Frequently Asked Questions

  1. What is CVE-2021-39189? CVE-2021-39189 is a medium-severity security vulnerability in pimcore/pimcore (composer), affecting versions < 10.1.3. It is fixed in 10.1.3.
  2. How severe is CVE-2021-39189? CVE-2021-39189 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of pimcore/pimcore are affected by CVE-2021-39189? pimcore/pimcore (composer) versions < 10.1.3 is affected.
  4. Is there a fix for CVE-2021-39189? Yes. CVE-2021-39189 is fixed in 10.1.3. Upgrade to this version or later.
  5. Is CVE-2021-39189 exploitable, and should I be worried? Whether CVE-2021-39189 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2021-39189 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2021-39189? Upgrade pimcore/pimcore to 10.1.3 or later.

Other vulnerabilities in pimcore/pimcore

CVE-2026-11407CVE-2026-5394CVE-2026-45704CVE-2026-45703CVE-2026-45260

Stop the waste.
Protect your environment with Kodem.