CVE-2020-15085: In Saleor Storefront before version 2.10.3, request data used to authenticate customers was inadvertently cach

Q: How do I fix CVE-2020-15085?

saleor: upgrade to 2.10.3. Exact commands for each OS are on this page.

Q: Is CVE-2020-15085 being exploited?

CVE-2020-15085 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2020-15085 affect?

CVE-2020-15085 affects saleor. Severity is medium (CVSS 6.9). 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 extra

Q: How urgent is CVE-2020-15085?

Priority 36/100. No elevated risk signals yet.

Routine

MEDIUM 6.9UPGRADE

CVE-2020-15085 is a medium-severity flaw (CVSS 6.9) affecting saleor. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 st

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.9 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.6% (top 52%)
CISA exploited list	No
Weakness	CWE-312
Published	2020-06-30
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: mirumee

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-06-30 17:15 UTCPublished CVE record published
2026-06-17 02:56 UTCUpdated Record last modified

mirumee saleor UPGRADE

Affected: < 2.10.3

Fixed in: 2.10.3

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy saleor || rpm -q saleor || saleor --version

2. UPGRADE to 2.10.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade saleor

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade saleor

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-15085?

saleor: upgrade to 2.10.3. Exact commands for each OS are on this page.

Is CVE-2020-15085 being exploited?

CVE-2020-15085 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-15085 affect?

CVE-2020-15085 affects saleor. Severity is medium (CVSS 6.9). 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 extra

How urgent is CVE-2020-15085?

Priority 36/100. No elevated risk signals yet.

Related CVEs

CVE-2026-33756 HIGH 7.5 UPGRADE Saleor is an e-commerce platform
CVE-2026-35401 HIGH 7.5 UPGRADE Saleor is an e-commerce platform
CVE-2026-35407 MEDIUM 6.5 UPGRADE Saleor is an e-commerce platform
CVE-2026-39851 MEDIUM 4.3 UPGRADE Saleor is an e-commerce platform
CVE-2026-24136 HIGH 7.5 UPGRADE Saleor is an e-commerce platform

References

← Back to latest CVEs