payloadcms payload up to 3.89.x/4.0.0-canary.33 plugin-multi-tenant arrayFieldAccess.create/arrayFieldAccess.update privileges management

Summaryinfo

A vulnerability marked as critical has been reported in payloadcms payload up to 3.89.x/4.0.0-canary.33. The impacted element is the function arrayFieldAccess.create/arrayFieldAccess.update of the component plugin-multi-tenant. This manipulation causes privileges management. This vulnerability is registered as CVE-2026-105860. Remote exploitation of the attack is possible. No exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability has been found in payloadcms payload up to 3.89.x/4.0.0-canary.33 and classified as critical. Affected by this vulnerability is the function arrayFieldAccess.create/arrayFieldAccess.update of the component plugin-multi-tenant. The manipulation with an unknown input leads to a privileges management vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Payload is a free and open source headless content management system. In @payloadcms/plugin-multi-tenant versions before 3.90.0 and canary versions before 4.0.0-canary.34, the default tenant array field access allows an authenticated user to assign the user's own account to other tenants. Deployments that replace the default behavior with secured tenants arrayFieldAccess.create and tenants arrayFieldAccess.update functions are not affected by this behavior. This issue is fixed in versions 3.90.0 and 4.0.0-canary.34.

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-105860 since 10/06/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.

Upgrading to version 3.90.0 or 4.0.0-canary.34 eliminates this vulnerability.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• payloadcms

Name

• payload

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

• Product: https://github.com/payloadcms/payload/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion