# CVE-2025-58442: Saleor has user enumeration vulnerability due to different error messages

> Attackers can enumerate valid user emails by observing distinct error messages during account registration in Saleor.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Sep 2025
- **Updated:** 10 Sep 2025
- **Also known as:** GHSA-8w67-mfm5-fwx5

## What is CVE-2025-58442?

CVE-2025-58442 is a medium-severity vulnerability in saleor, published on 9 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Saleor is an e-commerce platform. Starting in version 3.21.0 and prior to version 3.21.16, requesting certain fields in the response of `accountRegister` may result in errors that could unintentionally reveal whether a user with the provided email already exists in Saleor. Version 3.21.16 fixes the issue. As a workaround, rate-limit the mutation to reduce the impact.

Weakness: CWE-204 (Observable Response Discrepancy)

## Which versions are affected by CVE-2025-58442?


## How do I fix CVE-2025-58442?

No fix has been published for CVE-2025-58442 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-58442 being exploited?

There is no known exploitation of CVE-2025-58442 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-58442 and fix it if it is affected.

What it is: CVE-2025-58442 is a medium-severity vulnerability in saleor, published on 9 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-58442 in the wild and no public exploit code.

Affected product: saleor. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-58442/ (Markdown: https://insights.sbomify.com/CVE-2025-58442/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-58442
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-58442
- OSV: https://osv.dev/vulnerability/CVE-2025-58442

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-58442/
Summaries are generated and may contain mistakes; the official description above is the record.