# CVE-2026-55207: Pimcore: Account Takeover via Password Reset URL Injection allows unauthenticated attacker to hijack any admin account with 2FA bypass

> Unauthenticated attackers can hijack admin accounts and bypass 2FA by injecting a malicious URL into password reset requests, leading to full system compromise.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 9 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** GHSA-h854-c3m3-mh5v

## What is CVE-2026-55207?

CVE-2026-55207 is a high-severity authentication bypass vulnerability in pimcore, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Pimcore is an Open Source Data & Experience Management Platform. Prior to 2025.4.6 and 2026.1.6, an unauthenticated attacker who knows a valid admin username can take over any Pimcore admin account by sending a password reset request with an attacker-controlled resetPasswordUrl. The server generates a real cryptographic recovery token, appends it to the supplied URL, and emails the link to the victim; when the victim clicks the link, the token is sent to the attacker and can be used with POST /pimcore-studio/api/login/token to authenticate with full admin privileges while bypassing two-factor authentication. This issue is fixed in versions 2025.4.6 and 2026.1.6.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

## Which versions are affected by CVE-2026-55207?

4 open source packages ship an affected version, including pimcore/studio-backend-bundle.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pimcore/studio-backend-bundle` | Packagist | All versions | 2025.4.6 |
| `pimcore/studio-backend-bundle` | Packagist | All versions | 2025.4.6 |
| `pimcore/studio-backend-bundle` | Packagist | From 2026.1.0 | 2026.1.6 |
| `pimcore/studio-backend-bundle` | Packagist | From 2026.1.0 | 2026.1.6 |

## How do I fix CVE-2026-55207?

Upgrade pimcore/studio-backend-bundle to a fixed version for your release line: 2025.4.6 or 2026.1.6.

## Is CVE-2026-55207 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55207 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-55207 and fix it if it is affected.

What it is: CVE-2026-55207 is a high-severity authentication bypass vulnerability in pimcore, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55207 exists.

Affected packages and fixed versions:
- pimcore/studio-backend-bundle (Packagist): affected all versions; fixed in 2025.4.6
- pimcore/studio-backend-bundle (Packagist): affected all versions; fixed in 2025.4.6
- pimcore/studio-backend-bundle (Packagist): affected from 2026.1.0; fixed in 2026.1.6
- pimcore/studio-backend-bundle (Packagist): affected from 2026.1.0; fixed in 2026.1.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-55207/ (Markdown: https://insights.sbomify.com/CVE-2026-55207/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-55207
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-55207
- OSV: https://osv.dev/vulnerability/CVE-2026-55207

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-55207/
Summaries are generated and may contain mistakes; the official description above is the record.