LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24136: Saleor has an Insecure Direct Object Reference (IDOR) in GraphQL API

Saleor is an e-commerce platform. Versions 3.2.0 through 3.20.109, 3.21.0-a.0 through 3.21.44 and 3.22.0-a.0 through 3.22.28 have a n Insecure Direct Object Reference (IDOR) vulnerability that allows unauthenticated actors to extract sensitive information in plain text. Orders created before Saleor 3.2.0 could have PIIs exfiltrated. The issue has been patched in Saleor versions: 3.22.29, 3.21.45, and 3.20.110. To workaround, temporarily block non-staff users from fetching order information (the order() GraphQL query) using a WAF.

HighCVSS 8.7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Saleor e-commerce sites running affected versions may expose order details to unauthenticated users through the GraphQL API. The disclosed impact is sensitive information exposure in plain text, including PII from orders created before Saleor 3.2.0. This is a high-priority privacy and customer trust issue for affected stores.

Executive priority

Patch or isolate affected Saleor stores urgently. The business risk is customer data exposure without authentication, which can trigger privacy, support, and reputational impacts. No active exploitation is confirmed in the provided sources, but the vulnerability characteristics justify fast remediation.

Technical view

CVE-2026-24136 is a CWE-639 IDOR in Saleor’s GraphQL API, affecting Saleor 3.2.0-3.20.109, 3.21.0-a.0-3.21.44, and 3.22.0-a.0-3.22.28. CVSS v4.0 is 8.7. The issue is patched in 3.20.110, 3.21.45, and 3.22.29.

Likely exposure

Internet-facing Saleor deployments with public GraphQL API access are the primary concern, especially stores with historical orders. Exposure depends on running an affected version and allowing non-staff access to order information through the order() GraphQL query.

Exploitation context

The CVE describes unauthenticated extraction of sensitive information. The source bundle does not show CISA KEV listing or public evidence of active exploitation. Treat as readily exploitable because the CVSS indicates network access, low complexity, no privileges, and no user interaction.

Researcher notes

The advisory identifies an IDOR affecting the order() GraphQL query. Avoid assuming broader Saleor components are affected beyond the cited ranges. The public data names patches and a WAF workaround but does not provide evidence of exploitation in the wild.

Mitigation direction

  • Upgrade Saleor to 3.20.110, 3.21.45, or 3.22.29 as applicable.
  • If immediate upgrade is not possible, block non-staff order() GraphQL access using a WAF.
  • Review vendor advisory and commits before applying compensating controls.
  • Prioritize environments storing customer PII or legacy orders created before Saleor 3.2.0.

Validation and detection

  • Inventory Saleor instances and confirm exact deployed versions.
  • Check whether public GraphQL endpoints expose order information to non-staff users.
  • Verify patched versions are deployed after remediation.
  • Review access logs for unusual unauthenticated order information requests.
  • Confirm WAF rules block non-staff order() GraphQL requests if used.
Prepared
Confidence
high
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-639: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24136 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.7 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.7CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

8.7High
CVSS 4.0 vector shape for CVE-2026-24136Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
saleorsaleor>= 3.22.0-a.0, < 3.22.29, >= 3.21.0-a.0, < 3.21.45, >= 3.2.0, < 3.20.110Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.