Saleor Storefront
Approved changes feed: RSS · Atom
cpe:2.3:a:mirumee:saleor-storefront:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Mirumee (ab8988cd-468e-5cc9-b9f9-6633eb0299b4) |
|---|---|
| Product | Saleor Storefront (fdbc048a-6345-5d7b-a92a-edfe9544fe9d) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2020-15085 |
vulnerable | 2026-06-08 05:19:25.236930 |
Client caching login operation with plaintext password in Saleor Storefront
MEDIUM (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 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.
Published: 2020-06-30T16:25:13.000Z
Updated: 2024-08-04T13:08:22.044Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.