Reset Password / Login vulnerability in Sulu

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2020-15132: 1.11% estimated exploitation activity in the next 30 days; percentile 66.00 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact What kind of vulnerability is it? Who is impacted? This vulnerability consists of a few related issues: 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: 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: 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.…

Published by the source

5 Aug 2020, 21:27 UTC

Last modified by the source

9 Jan 2023, 05:03 UTC

Source last checked

26 Oct 2026, 13:56 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-wfm4-pq59-wg6r

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-15132

Advisory: Reset Password / Login vulnerability in Sulu
IDs: CVE-2020-15132, GHSA-wfm4-pq59-wg6r
Record: https://patchnext.com/advisories/cve-2020-15132 (revision 1, source checked 26 Oct 2026, 13:56 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: sulu/sulu 2.1.1, 2.0.10, 1.6.34. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist sulu/sulu: affected < 1.6.34; >= 2.0.0, < 2.0.10; >= 2.1.0, < 2.1.1; fixed in 2.0.10, 1.6.34, 2.1.1

## Suggested inspection (read-only)
- Packagist sulu/sulu: 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 sulu/sulu.
- 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://github.com/advisories/GHSA-wfm4-pq59-wg6r (GitHub-reviewed advisory GHSA-wfm4-pq59-wg6r lists affected ranges: Packagist sulu/sulu >=0 =2.0.0 =2.1.0 <2.1.1)

Commands are suggestions: review each one before running it.