Summary
Reset Password / Login vulnerability in Sulu
Forget password leaks information if the user exists
When the "Forget password" feature on the login screen is used, Sulu asks the user for a username or email address. If the given string is not found, a response with a 400 error code is returned, along with a error message saying that this user name does not exist:
{
"code": 0,
"message": "Entity with the type \u0022Sulu\\Bundle\\SecurityBundle\\Entity\\User\u0022 and the id \u0022asdf\u0022 not found."
}
This enables attackers to retrieve valid usernames.
Forgot password leaks user email if user exists
The response of the "Forgot Password" request returns the email address to which the email was sent, if the operation was successful:
{"email":"[email protected]"}
This information should not be exposed, as it can be used to gather email addresses.
Response time of login gives hint if the username exists
If the username the user enters in the login screen does not exists, the request responds much faster than if the username exists. This again allows attackers to retrieve valid usernames.
Reset Token for Forgot Password feature is not hashed
The reset token in the user database table is not hashed. That means that somebody could try to request a new password using the Forgot Password feature, and look that up in the database, if the attacker somehow got access to the database. Hashing the reset token would fix that problem.
Workarounds
Override the files manually in your project and change them accordingly.
Impact
What kind of vulnerability is it? Who is impacted?
This vulnerability consists of a few related issues:
CVE-2020-15132 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 (1.6.34, 2.0.10, 2.1.1); upgrading removes the vulnerable code path.
Affected versions
Security releases
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.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
This problem was fixed in Release 1.6.34, 2.0.10 and 2.1.1.
Frequently Asked Questions
- What is CVE-2020-15132? CVE-2020-15132 is a medium-severity security vulnerability in sulu/sulu (composer), affecting versions < 1.6.34. It is fixed in 1.6.34, 2.0.10, 2.1.1.
- How severe is CVE-2020-15132? CVE-2020-15132 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.
- Which versions of sulu/sulu are affected by CVE-2020-15132? sulu/sulu (composer) versions < 1.6.34 is affected.
- Is there a fix for CVE-2020-15132? Yes. CVE-2020-15132 is fixed in 1.6.34, 2.0.10, 2.1.1. Upgrade to this version or later.
- Is CVE-2020-15132 exploitable, and should I be worried? Whether CVE-2020-15132 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
- What actually determines whether CVE-2020-15132 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.
- How do I fix CVE-2020-15132?
- Upgrade
sulu/suluto 1.6.34 or later - Upgrade
sulu/suluto 2.0.10 or later - Upgrade
sulu/suluto 2.1.1 or later
- Upgrade