Pimcore: Account Takeover via Password Reset URL Injection allows unauthenticated attacker to hijack any admin account with 2FA bypass
CVE-2026-55207GHSA-h854-c3m3-mh5v
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (pimcore/studio-backend-bundle 2026.1.6, 2025.4.6), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Packagist pimcore/studio-backend-bundle
- Affected
- < 2025.4.6>= 2026.1.0, < 2026.1.6
- Fixed in
- 2026.1.6, 2025.4.6
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-h854-c3m3-mh5v lists affected ranges: Packagist pimcore/studio-backend-bundle >=0 =2026.1.0 <2026.1.6 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-h854-c3m3-mh5v lists affected ranges: Packagist pimcore/studio-backend-bundle >=0 =2026.1.0 <2026.1.6
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 8.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- EPSS
- CVE-2026-55207: 0.67% estimated exploitation activity in the next 30 days; percentile 51.87 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary An unauthenticated attacker takes 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 attacker's URL, and emails the link to the victim. When the victim clicks the link in their email, the token is sent to the attacker's server. The attacker then uses POST /pimcore-studio/api/login/token to authenticate as the victim with full admin privileges. Token login explicitly disables two-factor authentication, so even accounts with TOTP/Google Authenticator are compromised. Vulnerability Details Unauthenticated Endpoint Accepts Attacker URL The reset password endpoint at src/User/Controller/ResetPasswordController.php line 53 is public (uses PUBLICSTUDIOAPI voter). The ResetPassword schema at src/User/Schema/ResetPassword.php accepts a resetPasswordUrl string as a required parameter with zero validation. No URL scheme check, no domain allowlist, no…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-h854-c3m3-mh5v
- Revision 1 · created ·
Published from osv record GHSA-h854-c3m3-mh5v
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-55207 Advisory: Pimcore: Account Takeover via Password Reset URL Injection allows unauthenticated attacker to hijack any admin account with 2FA bypass IDs: CVE-2026-55207, GHSA-h854-c3m3-mh5v Record: https://patchnext.com/advisories/cve-2026-55207 (revision 2, source checked 26 Oct 2026, 14:50 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 8.8) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: pimcore/studio-backend-bundle 2026.1.6, 2025.4.6. A vendor fix does not mean a deployment is fixed. ## Affected components - Packagist pimcore/studio-backend-bundle: affected < 2025.4.6; >= 2026.1.0, < 2026.1.6; fixed in 2026.1.6, 2025.4.6 ## Suggested inspection (read-only) - Packagist pimcore/studio-backend-bundle: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on pimcore/studio-backend-bundle. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-h854-c3m3-mh5v (OSV record GHSA-h854-c3m3-mh5v lists affected ranges: Packagist pimcore/studio-backend-bundle >=0 =2026.1.0 <2026.1.6 (fixed)) - Verified: https://github.com/advisories/GHSA-h854-c3m3-mh5v (GitHub-reviewed advisory GHSA-h854-c3m3-mh5v lists affected ranges: Packagist pimcore/studio-backend-bundle >=0 =2026.1.0 <2026.1.6) Commands are suggestions: review each one before running it.
Loading voting…