CVE-2026-48744 json
Saleor: Anonymous users can modify channel settings via `channelUpdate` due to `all([])` bypass in permission check
published 3mo ago modified last mo. also EUVD-2026-61068 , GHSA-xqqq-qhgq-gx53
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository saleor/saleor. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 32%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- saleor saleor 3.21.67, 3.22.63, 3.23.22
- github.com/saleor/saleor@11efb4e commit
- github.com/saleor/saleor@580b93b commit
- github.com/saleor/saleor@9b1f59b commit
- github.com/saleor/saleor@afd1ddd commit
- github.com/saleor/saleor/releases/tag/3.21.67 release
- github.com/saleor/saleor/releases/tag/3.22.63 release
- github.com/saleor/saleor/releases/tag/3.23.22 release
Is CVE-2026-48744 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2mo ago
Exploit prediction
0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
Affected products
- saleor saleor
Classification
- Weakness
-
- CWE-285 Improper Authorization
References
- github.com /saleor/saleor/commit/11efb4e9ea76942cf142bc01de8846cbaf764465
- github.com /saleor/saleor/commit/580b93b6e0faef7800e667f0c3bc507d3ef6f5f5
- github.com /saleor/saleor/commit/9b1f59b3ed86c3fad3ce071639cf434c1ab94a85
- github.com /saleor/saleor/commit/afd1ddd13b79e78db4e05f846b1f159078c50417
-
github.com
/saleor/saleor/security/advisories/GHSA-xqqq-qhgq-gx53
advisory
- github.com /saleor/saleor/releases/tag/3.21.67
- github.com /saleor/saleor/releases/tag/3.22.63
- github.com /saleor/saleor/releases/tag/3.23.22
Sources
- CVE List CVE-2026-48744
- NVD CVE-2026-48744
- Maintainer advisory GHSA-xqqq-qhgq-gx53
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of saleor/saleor published their own advisory on GitHub. Reviewed sources take precedence over it.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.