Saleor up to 3.20.107/3.21.42/3.22.26 Refresh Token cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Saleor up to 3.20.107/3.21.42/3.22.26. It has been rated as problematic. This affects an unknown function of the component Refresh Token Handler. The manipulation leads to cross site scripting. This vulnerability is documented as CVE-2026-22849. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is advised.
Details
A vulnerability was found in Saleor up to 3.20.107/3.21.42/3.22.26. It has been rated as problematic. This issue affects an unknown function of the component Refresh Token Handler. The manipulation with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-83. The product does not neutralize or incorrectly neutralizes "javascript:" or other URIs from dangerous attributes within tags, such as onmouseover, onload, onerror, or style. Impacted is integrity. The summary by CVE is:
Saleor is an e-commerce platform. Starting in version 3.0.0 and prior to versions 3.20.108, 3.21.43, and 3.22.27, Saleor was allowing users to modify rich text fields with HTML without running any backend HTML cleaners thus allowing malicious actors to perform stored XSS attacks on dashboards and storefronts. Malicious staff members could craft script injections to target other staff members, possibly stealing their access and/or refresh tokens. This issue has been patched in versions 3.22.27, 3.21.43, and 3.20.108. In case of inability to upgrade straight away, a possible workaround is to use client-side cleaner.
It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-22849 since 01/12/2026. The exploitation is known to be easy. The attack may be initiated remotely. The exploitation needs additional levels of successful authentication. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK.
Upgrading to version 3.20.108, 3.21.43 or 3.22.27 eliminates this vulnerability. Applying the patch 1085c7813224a0a65f1dac7275cbc3244e23c386 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-3777). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
- 3.20.107
- 3.21.0
- 3.21.1
- 3.21.2
- 3.21.3
- 3.21.4
- 3.21.5
- 3.21.6
- 3.21.7
- 3.21.8
- 3.21.9
- 3.21.10
- 3.21.11
- 3.21.12
- 3.21.13
- 3.21.14
- 3.21.15
- 3.21.16
- 3.21.17
- 3.21.18
- 3.21.19
- 3.21.20
- 3.21.21
- 3.21.22
- 3.21.23
- 3.21.24
- 3.21.25
- 3.21.26
- 3.21.27
- 3.21.28
- 3.21.29
- 3.21.30
- 3.21.31
- 3.21.32
- 3.21.33
- 3.21.34
- 3.21.35
- 3.21.36
- 3.21.37
- 3.21.38
- 3.21.39
- 3.21.40
- 3.21.41
- 3.21.42
- 3.22.0
- 3.22.1
- 3.22.2
- 3.22.3
- 3.22.4
- 3.22.5
- 3.22.6
- 3.22.7
- 3.22.8
- 3.22.9
- 3.22.10
- 3.22.11
- 3.22.12
- 3.22.13
- 3.22.14
- 3.22.15
- 3.22.16
- 3.22.17
- 3.22.18
- 3.22.19
- 3.22.20
- 3.22.21
- 3.22.22
- 3.22.23
- 3.22.24
- 3.22.25
- 3.22.26
License
Website
- Product: https://github.com/saleor/saleor/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 3.6VulDB Meta Temp Score: 3.5
VulDB Base Score: 2.4
VulDB Temp Score: 2.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 4.8
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Cross site scriptingCWE: CWE-83 / CWE-79 / CWE-94
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Saleor 3.20.108/3.21.43/3.22.27
Patch: 1085c7813224a0a65f1dac7275cbc3244e23c386
Timeline
01/12/2026 CVE reserved01/21/2026 VulDB entry created
01/22/2026 Advisory disclosed
01/30/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-8jcj-r5g2-qrpv
Status: Confirmed
CVE: CVE-2026-22849 (🔒)
GCVE (CVE): GCVE-0-2026-22849
GCVE (VulDB): GCVE-100-342251
EUVD: 🔒
Entry
Created: 01/22/2026 00:54Updated: 01/30/2026 00:21
Changes: 01/22/2026 00:54 (68), 01/22/2026 07:38 (1), 01/30/2026 00:21 (11)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.