CVE-2026-108260 in Tina
Summary
by MITRE • 10/09/2026
Tina is a headless content management system. Prior to 0.2.1, the tina-markdown element in packages/@tinacms/web-components/src/tina-markdown.js assigns a rich-text node.url value directly to an anchor href without validating the URL scheme. A content author can store a link using a script-capable scheme, and a visitor who clicks the rendered link executes attacker-controlled script in the site's origin. The script can access same-origin application data and, when the visitor is an editor or administrator, may expose credentials stored by the TinaCMS admin on that origin. This issue is fixed in version 0.2.1.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 10/09/2026
The vulnerability identified as a Cross-Site Scripting (XSS) flaw resides within the tina-markdown element of the Tina headless content management system, specifically affecting versions prior to 0.2.1. This component is responsible for rendering markdown content into HTML structures that are displayed to end-users on websites powered by TinaCMS. The core technical failure lies in how the application handles URL schemes when processing rich-text nodes. When a content author creates a link within the CMS, the system extracts the url value from the node and directly assigns it to the href attribute of an anchor tag without performing any validation or sanitization of the scheme. This lack of input validation allows for the injection of malicious payloads disguised as valid URLs.
The operational impact of this vulnerability is significant because it enables stored XSS attacks that persist in the database until remediated. An attacker with content authoring privileges can embed a script-capable URL scheme, such as javascript:, into their published content. When a visitor navigates to a page containing this malicious link and clicks on it, the browser interprets the href value as executable code rather than a navigation target. This results in the execution of arbitrary JavaScript within the context of the victim site's origin. Because the script runs with full privileges associated with that domain, it can access sensitive same-origin application data, including cookies, local storage, and session tokens.
The severity is further amplified by the potential exposure of administrative credentials. If a user who has editor or administrator rights for the TinaCMS instance clicks on the malicious link, the injected script gains access to any credentials stored locally by the TinaCMS admin interface in that browser session. This could lead to unauthorized control over the content management system, allowing attackers to deface websites, inject further malware, or pivot into other internal systems if they share authentication mechanisms. The attack vector is primarily client-side and requires user interaction, classifying it under specific categories of web application vulnerabilities.
From a classification perspective, this vulnerability aligns with CWE-79, which describes Improper Neutralization of Input During Web Page Generation commonly known as Cross-site Scripting. Specifically, the flaw represents an unvalidated redirect or link injection scenario where the input is not sanitized before being used in HTML attributes. In terms of offensive security frameworks, this behavior corresponds to ATT&CK technique T1059, Command and Scripting Interpreter, specifically within the context of client-side execution via browser-based scripting languages like JavaScript. The exploitation relies on social engineering or trusted content placement to trigger the payload upon user interaction.
To mitigate this vulnerability, organizations must upgrade immediately to version 0.2.1 or later, where the issue has been resolved through proper input validation and output encoding practices. For environments that cannot yet update, a temporary mitigation involves implementing strict Content Security Policy headers that restrict script execution from unauthorized sources and disable inline scripts if feasible. Additionally, developers should ensure that all user-supplied data used in HTML attributes is properly encoded to prevent interpretation as executable code. Regular security audits of content management systems are essential to identify similar patterns where raw input is directly bound to DOM properties without sanitization.