Payload CMS up to 3.89.x/4.0.0-canary.33 File Cleanup unrestricted upload
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in Payload CMS Payload up to 3.89.x/4.0.0-canary.33. This issue affects some unknown processing of the component File Cleanup. Executing a manipulation can lead to unrestricted upload. This vulnerability is tracked as CVE-2026-105865. The attack can be launched remotely. No exploit exists. It is advisable to upgrade the affected component.
Details
A vulnerability classified as problematic was found in Payload CMS Payload up to 3.89.x/4.0.0-canary.33. This vulnerability affects an unknown functionality of the component File Cleanup. The manipulation with an unknown input leads to a unrestricted upload vulnerability. The CWE definition for the vulnerability is CWE-434. The product allows the attacker to upload or transfer files of dangerous types that can be automatically processed within the product's environment. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
Payload is a free and open source headless content management system. In versions before 3.90.0 and canary versions before 4.0.0-canary.34, an authenticated user who can update or delete uploads stored locally can cause file cleanup to remove unintended files outside the configured upload directory, resulting in data loss or service disruption. Deployments that restrict upload management to trusted users are less exposed. This issue is fixed in versions 3.90.0 and 4.0.0-canary.34.
The advisory is shared for download at github.com. This vulnerability was named CVE-2026-105865 since 10/06/2026. The exploitation appears to be easy. The attack can be initiated remotely. Additional levels of successful authentication are required for exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1608.002.
Upgrading to version 3.90.0 or 4.0.0-canary.34 eliminates this vulnerability.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
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
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 4.7
VulDB Temp Score: 4.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.1
CNA Vector (GitHub_M): 🔒
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: Unrestricted uploadCWE: CWE-434 / CWE-284 / 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
Advisory: github.comStatus: Confirmed
CNA: GitHub_M
CVE: CVE-2026-105865 (🔒)
GCVE (CVE): GCVE-0-2026-105865
GCVE (VulDB): GCVE-100-414352
Entry
Created: 10/06/2026 19:10Changes: 10/06/2026 19:10 (65)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.