CVE-2026-105868 in Payload
Summary
by MITRE • 10/06/2026
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, local upload configurations that accept XML files can store an XML file and stylesheet that execute JavaScript in the Payload origin when a logged-in user opens the file. This issue is fixed in versions 3.90.0 and 4.0.0-canary.34.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 10/06/2026
Payload, a widely adopted free and open-source headless content management system, contains a critical security vulnerability affecting local upload configurations that accept XML files. In software versions prior to 3.90.0 and canary releases before 4.0.0-canary.34, the application fails to adequately sanitize or restrict the types of content within uploaded XML documents when processed by authenticated users. This flaw allows an attacker who has valid credentials for a logged-in user account to upload a specially crafted XML file accompanied by an external stylesheet. When another authorized user opens this specific file through the Payload interface, the browser interprets the embedded instructions and executes JavaScript code within the context of the Payload origin.
The technical nature of this vulnerability aligns with CWE-79, which classifies it as Cross-Site Scripting (XSS). Specifically, because the execution occurs in a trusted environment after authentication, it represents an authenticated or stored XSS scenario depending on whether the payload is persisted for later retrieval by other users or executed immediately upon upload. The mechanism relies on the browser's native ability to process XML and apply XSLT stylesheets, which can contain script tags that are then evaluated by the JavaScript engine. Since this execution happens in the Payload origin, it grants the malicious script full access to cookies, session tokens, local storage data, and other sensitive information associated with the user’s active session on the CMS platform.
The operational impact of this vulnerability is severe for organizations relying on Payload for content management. An attacker can leverage this flaw to hijack administrative sessions, leading to unauthorized modification or deletion of content, injection of malicious links into published articles, or defacement of the public-facing website if such data is rendered without further sanitization. Furthermore, because the attack vector requires a logged-in user to open the file, it facilitates targeted social engineering attacks where an attacker might trick specific high-privilege users into viewing compromised documents. This undermines the integrity and confidentiality guarantees provided by the authentication layer of the CMS.
To mitigate this risk, organizations must immediately upgrade their Payload instances to version 3.90.0 or later, which includes patches for canary versions up to 4.0.0-canary.34. These updates implement stricter validation rules that prevent the execution of scripts within uploaded XML files by either stripping out dangerous elements or enforcing a Content Security Policy that blocks inline script execution in this context. Additionally, administrators should review upload configurations to ensure that only necessary file types are accepted and consider implementing server-side sanitization for all user-uploaded content before it is stored or served. Monitoring logs for unusual XML uploads can also help detect attempted exploitation of this vulnerability in real-time.