PayloadCMS up to 3.89.x/4.0.0-canary.33 Stripe payment adapter logic error
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 1.52- |
Summary
A vulnerability categorized as problematic has been discovered in PayloadCMS up to 3.89.x/4.0.0-canary.33. Affected by this issue is some unknown functionality of the component Stripe payment adapter. Such manipulation leads to logic error. This vulnerability is listed as CVE-2026-105850. The attack may be performed from remote. There is no available exploit. It is advisable to upgrade the affected component.
Details
A vulnerability was found in PayloadCMS up to 3.89.x/4.0.0-canary.33 and classified as problematic. Affected by this issue is an unknown functionality of the component Stripe payment adapter. The manipulation with an unknown input leads to a logic error vulnerability. Using CWE to declare the problem leads to CWE-840. Impacted is integrity.
This vulnerability is handled as CVE-2026-105850. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. The technical details are unknown and an exploit is not available.
Upgrading to version 3.90.0 or 4.0.0-canary.34 eliminates this vulnerability.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
- 3.0
- 3.1
- 3.2
- 3.3
- 3.4
- 3.5
- 3.6
- 3.7
- 3.8
- 3.9
- 3.10
- 3.11
- 3.12
- 3.13
- 3.14
- 3.15
- 3.16
- 3.17
- 3.18
- 3.19
- 3.20
- 3.21
- 3.22
- 3.23
- 3.24
- 3.25
- 3.26
- 3.27
- 3.28
- 3.29
- 3.30
- 3.31
- 3.32
- 3.33
- 3.34
- 3.35
- 3.36
- 3.37
- 3.38
- 3.39
- 3.40
- 3.41
- 3.42
- 3.43
- 3.44
- 3.45
- 3.46
- 3.47
- 3.48
- 3.49
- 3.50
- 3.51
- 3.52
- 3.53
- 3.54
- 3.55
- 3.56
- 3.57
- 3.58
- 3.59
- 3.60
- 3.61
- 3.62
- 3.63
- 3.64
- 3.65
- 3.66
- 3.67
- 3.68
- 3.69
- 3.70
- 3.71
- 3.72
- 3.73
- 3.74
- 3.75
- 3.76
- 3.77
- 3.78
- 3.79
- 3.80
- 3.81
- 3.82
- 3.83
- 3.84
- 3.85
- 3.86
- 3.87
- 3.88
- 3.89
- 4.0.0-canary.0
- 4.0.0-canary.1
- 4.0.0-canary.2
- 4.0.0-canary.3
- 4.0.0-canary.4
- 4.0.0-canary.5
- 4.0.0-canary.6
- 4.0.0-canary.7
- 4.0.0-canary.8
- 4.0.0-canary.9
- 4.0.0-canary.10
- 4.0.0-canary.11
- 4.0.0-canary.12
- 4.0.0-canary.13
- 4.0.0-canary.14
- 4.0.0-canary.15
- 4.0.0-canary.16
- 4.0.0-canary.17
- 4.0.0-canary.18
- 4.0.0-canary.19
- 4.0.0-canary.20
- 4.0.0-canary.21
- 4.0.0-canary.22
- 4.0.0-canary.23
- 4.0.0-canary.24
- 4.0.0-canary.25
- 4.0.0-canary.26
- 4.0.0-canary.27
- 4.0.0-canary.28
- 4.0.0-canary.29
- 4.0.0-canary.30
- 4.0.0-canary.31
- 4.0.0-canary.32
- 4.0.0-canary.33
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: Logic errorCWE: CWE-840
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
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: PayloadCMS 3.90.0/4.0.0-canary.34
Timeline
10/06/2026 Advisory disclosed10/06/2026 VulDB entry created
10/06/2026 VulDB entry last update
Sources
Status: ConfirmedCVE: CVE-2026-105850 (🔒)
GCVE (CVE): GCVE-0-2026-105850
GCVE (VulDB): GCVE-100-414338
Entry
Created: 10/06/2026 18:40Changes: 10/06/2026 18:40 (49)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.