CVE-2026-48744 — Saleor: Anonymous users can modify channel settings via `channelUpdate` due to `all([])` bypass in permission check
Saleor is an e-commerce platform. From 3.14.67 until 3.21.67, 3.22.63, and 3.23.22, a broken authorization check in saleor/permission/utils.py can incorrectly authorize unauthenticated GraphQL requests. The flaw permits anonymous callers to use the channelUpdate() mutation to change channel order settings such as allowUnpaidOrders even when the response reports PermissionDenied. The same permission utility can expose hidden objects through the pageType() and translation() queries, including attributes whose visibleInStorefront field is false and that should be visible only to users with management permissions. This issue is fixed in versions 3.21.67, 3.22.63, and 3.23.22.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Technical severity (medium)+3
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Saleor Saleor).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 6.5 | CVSS 3.1 | Medium | 3.9 | 2.5 | security-advisories@github.com via NIST National Vulnerability Database |
| 6.5 | CVSS 3.1 | Medium | — | — | GitHub_M via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N (score shown at the top: security-advisories@github.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Audit administrative actions and access to resources outside each user’s normal pattern.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · saleor/saleor
- SSVC assessment updated
- Record published
- CVSS changed · 6.5
- Source status changed · → Deferred
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- github.com/saleor/saleor/releases/tag/3.23.22
- github.com/saleor/saleor/commit/11efb4e9ea76942cf142bc01de8846cbaf764465
- github.com/saleor/saleor/commit/580b93b6e0faef7800e667f0c3bc507d3ef6f5f5
- github.com/saleor/saleor/releases/tag/3.21.67
- github.com/saleor/saleor/releases/tag/3.22.63
- github.com/saleor/saleor/commit/afd1ddd13b79e78db4e05f846b1f159078c50417
- github.com/saleor/saleor/security/advisories/GHSA-xqqq-qhgq-gx53
- github.com/saleor/saleor/commit/9b1f59b3ed86c3fad3ce071639cf434c1ab94a85
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-44472 Saleor: Account pre-hijacking vulnerability due to unverified anonymous order merge Aug 18, 2026
- Medium CVE-2026-39851 Saleor has a user enumeration vulnerability due to different error messages Apr 8, 2026
- Medium CVE-2026-35407 Saleor has Cross-Account Email Change via Unbound Confirmation Token Apr 8, 2026
- High CVE-2026-35401 Saleor has a resource exhaustion vulnerability in GraphQL queries Apr 8, 2026
- High CVE-2026-33756 Saleor Affected by Denial of Service via Unbounded GraphQL Query Batching Apr 8, 2026
- High CVE-2026-24136 Saleor has an Insecure Direct Object Reference (IDOR) in GraphQL API Jan 23, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No FIRST EPSS score.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-48744 is "Saleor: Anonymous users can modify channel settings via `channelUpdate` due to `all([])` bypass in permission check", rated Medium. It affects Saleor (Saleor); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.5 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.