CVE-2019-7950

N/A

Published: August 2, 2019 at 09:35 PM UTC

Updated: June 17, 2026 at 02:41 AM UTC

1 product affected across 1 vendorMagento

Using Magento 2 by N/A?

Get instant alerts when new vulnerabilities affect Magento 2 - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

N/A

Exploit prediction

EPSS 2%

Description

An access control bypass vulnerability exists in Magento 2.1 prior to 2.1.18, Magento 2.2 prior to 2.2.9, Magento 2.3 prior to 2.3.2. An unauthenticated user can bypass access controls via REST API calls to assign themselves to an arbitrary company, thereby gaining read access to potentially confidental information.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Magento · Magento

95%

v < 2.1.182.1.0 ≤ v < 2.1.182.2.0 ≤ v < 2.2.92.3.0 ≤ v < 2.3.2

Affected range stops below 2.1.18, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.2.9, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.3.2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

https://magento.com/security/patches/magento-2.3.2-2.2.9-and-2.1.18-security-update-13

References (1)

x_refsource_CONFIRMVendor Advisory

Source: [email protected]

https://magento.com/security/patches/magento-2.3.2-2.2.9-and-2.1.18-security-update-13

CVSS

5MEDIUM[email protected]

Confidentiality: PARTIAL
Integrity: NONE
Availability: NONE

Vector?

Quick Info

StatusMODIFIED

CWE

CWE-639

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card