CVE-2026-45701
Weak Password Reset Token and API Key Generation in Sulu
Publication date: 2026-06-01
Last updated on: 2026-06-01
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| sulu | sulu | to 2.6.23|end_excluding=3.0.6 (exc) |
| sulu | sulu | to 2.6.23 (exc) |
| sulu | sulu | to 3.0.6 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-327 | The product uses a broken or risky cryptographic algorithm or protocol. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-45701 is a security vulnerability in the Sulu content management system where weak cryptographic algorithms were used for generating password reset tokens and API keys.
This weakness means that the cryptographic hash algorithm employed was broken or risky, potentially allowing attackers to compromise these tokens or keys.
The issue affects Sulu versions prior to 2.6.23 and 3.0.6 and has been patched in those versions.
How can this vulnerability impact me? :
Because the vulnerability involves weak cryptographic algorithms for password reset tokens and API keys, an attacker could potentially exploit this to gain unauthorized access to user accounts or API functionalities.
This could lead to account compromise, unauthorized actions within the CMS, and potential data exposure or manipulation.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability relates to the use of weak cryptographic algorithms in the generation of password reset tokens and API keys within the Sulu CMS. Detection would involve inspecting the version of Sulu CMS in use and reviewing the relevant code files for the presence of the weak cryptographic algorithm.
Specifically, you can check the installed Sulu CMS version to see if it is older than 2.6.23 or 3.0.6, which are the patched versions.
Example commands to detect vulnerable versions:
- Check the Sulu CMS version via composer (if used): composer show sulu/sulu | grep versions
- Search for the presence of weak hash functions in the SecurityBundle files (User.php and ResettingController.php) using grep or similar tools, e.g.: grep -E 'md5|sha1' path/to/SecurityBundle/
Note: The advisory does not provide explicit detection commands or network indicators.
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation step is to upgrade the Sulu CMS to version 2.6.23 or 3.0.6 or later, where the vulnerability has been patched.
As a temporary workaround before upgrading, you can manually patch the User.php and ResettingController.php files in the SecurityBundle to replace the weak cryptographic algorithms with stronger ones.
It is recommended to review the security advisory and coordinate with your development team to apply these patches or upgrades promptly.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability involves the use of weak cryptographic algorithms for generating password reset tokens and API keys in Sulu CMS versions prior to 2.6.23 and 3.0.6.
Weak cryptographic algorithms can potentially lead to unauthorized access or compromise of sensitive user credentials, which may impact the security and privacy of user data.
Such security weaknesses could affect compliance with standards and regulations like GDPR and HIPAA, which require adequate protection of personal and sensitive data through strong security controls.
However, the provided information does not explicitly discuss the direct impact of this vulnerability on compliance with these regulations.