Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

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

45
This week
MEDIUM 5.3REMOTEUPGRADE

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

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 s

Why this priority

  • Public exploit reference
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score5.3 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance1.2% (top 33%)
CISA exploited listNo
WeaknessCWE-862
Published2019-07-15
Last modified2026-06-17
Publisher (CNA): DWF · Vendor: mirumee

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

mirumee saleor UPGRADE
Affected: >= 2.0.0 and < 2.3.1
Fixed in: 2.3.1
Safe to downgrade to: a release before 2.0.0
1. Check installed version
apt-cache policy saleor || rpm -q saleor || saleor --version
2. UPGRADE to 2.3.1 (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.
3. If no update is available yet, DOWNGRADE to a release before 2.0.0 (Debian / Ubuntu)
apt-cache madison saleor sudo apt install saleor=<VERSION_BEFORE_2.0.0> sudo apt-mark hold saleor
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list saleor sudo dnf downgrade saleor-<VERSION_BEFORE_2.0.0> sudo dnf versionlock add saleor
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
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-2019-1010304?

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

Is CVE-2019-1010304 being exploited?

CVE-2019-1010304 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-2019-1010304 affect?

CVE-2019-1010304 affects saleor. Severity is medium (CVSS 5.3). 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 ty

How urgent is CVE-2019-1010304?

Priority 45/100. Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.