CVE-2024-23648: Host header injection in the password reset
Summary The password reset functionality sends to the the user requesting a password change an email containing an URL to reset its password. The URL sent contains a unique token, valid during 24 hours, allowing the user to reset its password. This token is highly sensitive ; as an attacker able to retrieve it would be able to resets the user's password.
Published Jan 24, 2024
Affected packages
pimcore/admin-ui-classic-bundle
- Ecosystem
- Composer (PHP)
- Affected
- < 1.2.3
- Fixed in
- 1.2.3
- Check
composer show pimcore/admin-ui-classic-bundle
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
The password reset functionality sends to the the user requesting a password change an email containing an URL to reset its password.
The URL sent contains a unique token, valid during 24 hours, allowing the user to reset its password. This token is highly sensitive ; as an attacker able to retrieve it would be able to resets the user's password.
It was identified during the audit that the reset-password URL is crafted using the "Host" HTTP header of the request sent to request a password reset.
This way, an external attacker could send password requests for users, but specify a "Host" header of a website that they control. If the user receiving the mail clicks on the link, the attacker would retrieve the reset token of the victim and perform account takeover.
Details
This attack required the server to serve Pimcore on arbitrary "Host". This configuration would be plausible if the attacker is already behind the reverse proxy. During the assessment of my client, their instance was accepting any Host header, and they did not received security recommendations that they should restrict this while installing Pimcore.
From what I understood of Pimcore, the vulnerability is in the "admin-ui-classic-bundle", in the file src/Controller/Admin/UserController.php.
The following screenshots provide evidences of the vulnerability. The environment of the test is : dockerized Pimcore v11.1.1 on default configuration (https://pimcore.com/docs/platform/Pimcore/Getting_Started/Installation/Docker_Based_Installation/).
PoC
image image
Remediation
Create a variable that sets the server host. Don't enable password reset functionality while this variable is not set ; or make sure that the administrator knows what they are doing.
I believe that just documenting that the server should not serve on any Host would not be enough to enforce a remediation to this vulnerability.
The Snipe-IT project managed this same issue by creating a "APP_ALLOW_INSECURE_HOSTS" variable, and retrieving the app absolute URL from a config file : https://github.com/snipe/snipe-it/commit/0c4768fd2a11ac26a61814cef23a71061bfd8bcc
Impact
Could lead to a 1-click account takeover
Credited to Mathisca.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-44741
Pimcore Admin Classic Bundle Vulnerable to SQL Injection in Translation Grid Date Filter via Unsanitized Property Parameter
high8.8May 27, 2026CVE-2026-23495
Pimcore's Admin Classic Bundle is Missing Function Level Authorization on "Predefined Properties" Listing
medium4.3Jan 15, 2026CVE-2025-30166
Pimcore's Admin Classic Bundle allows HTML Injection
low1.8Apr 8, 2025CVE-2025-24980
Pimcore Admin Classic Bundle allows user enumeration
medium6.9Feb 7, 2025GHSA-hq76-662x-7mw4
Pimcore includes vulnerable PHPOffice/PhpSpreadsheet
high8.8Sep 3, 2024CVE-2024-41109
Pimcore vulnerable to disclosure of system and database information behind /admin firewall
medium6.3Jul 30, 2024
