payloadcms Payload up to 3.89.x/4.0.0-canary.33 Duplicate Operation disableDuplicate privileges management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in payloadcms Payload up to 3.89.x/4.0.0-canary.33 and classified as critical. The impacted element is an unknown function of the component Duplicate Operation. Performing a manipulation of the argument disableDuplicate results in privileges management. This vulnerability was named CVE-2026-105851. The attack may be initiated remotely. There is no available exploit. The affected component should be upgraded.
Details
A vulnerability classified as critical has been found in payloadcms Payload up to 3.89.x/4.0.0-canary.33. This affects an unknown part of the component Duplicate Operation. The manipulation of the argument disableDuplicate with an unknown input leads to a privileges management vulnerability. CWE is classifying the issue as CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Payload is a free and open source headless content management system. In versions from 3.0.0 before 3.90.0 and canary versions before 4.0.0-canary.34, the duplicate operation copies values from a source document even when a field is hidden or its access.read or access.create rule rejects that value for the caller. The disableDuplicate setting does not prevent this access-control bypass. This issue is fixed in versions 3.90.0 and 4.0.0-canary.34.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-105851 since 10/06/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
Upgrading to version 3.90.0 or 4.0.0-canary.34 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
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
Website
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: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
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: Privileges managementCWE: CWE-269 / CWE-266
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: Payload 3.90.0/4.0.0-canary.34
Timeline
10/06/2026 Advisory disclosed10/06/2026 CVE reserved
10/06/2026 VulDB entry created
10/06/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CNA: GitHub_M
CVE: CVE-2026-105851 (🔒)
GCVE (CVE): GCVE-0-2026-105851
GCVE (VulDB): GCVE-100-414333
Entry
Created: 10/06/2026 18:34Changes: 10/06/2026 18:34 (68)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.