Tinacms
CVE-2025-68278
HIGH
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Impact | Authenticated users can inject arbitrary code via malicious markdown content processed by gray-matter, achieving RCE with high impact. CVSS 7.3 reflects high confidentiality/integrity damage. Moderate observed exploitation activity. Attack requires user interaction and authenticated access, limiting immediate blast radius but posing significant risk to self-hosted or multi-user CMS deployments. |
| Exploit ScenarioDerived | Authenticated attacker uploads markdown file with malicious YAML frontmatter exploiting gray-matter parser. Upon content processing/rendering (requires admin interaction), arbitrary code executes server-side. Publicly available exploit code exists demonstrating payload injection technique. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 10, 2026
Remote code execution in TinaCMS affects versions prior to 3.1.1, @tinacms/cli before 2.0.4, and @tinacms/graphql before 2.0.3. Authenticated attackers with content control over markdown files can execute arbitrary code through insecure gray-matter package usage. The vulnerability requires low-privilege authentication (PR:L) and user interaction (UI:P), enabling full compromise of confidentiality, integrity, and availability in the vulnerable context. Publicly available exploit code exists, significantly increasing deployment risk for unpatched installations managing user-contributed markdown content.
RemediationAI
Vendor-released patches: upgrade TinaCMS to version 3.1.1 or later, @tinacms/cli to version 2.0.4 or later, and @tinacms/graphql to version 2.0.3 or later. All three packages must be updated simultaneously to eliminate exposure. Organizations unable to immediately patch should restrict markdown content editing permissions to fully trusted administrators only and implement strict content review workflows. Implement input validation on frontmatter fields if custom parsing exists. Consult GitHub Security Advisory GHSA-529f-9qwm-9628 (https://github.com/tinacms/tinacms/security/advisories/GHSA-529f-9qwm-9628) for complete vendor guidance and technical details on the gray-matter exploitation mechanism. Verify remediation commit fa7c27abef968e3f3a3e7d564f282bc566087569 is included in deployed versions.
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 3 packages in npm
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CWE-94 code injection stems from unsafe gray-matter frontmatter parsing in markdown processing pipeline. The library permits YAML deserialization of attacker-controlled markdown headers without input sanitization, enabling constructor injection or prototype pollution leading to arbitrary Node.js code execution during content ingestion workflows.
Know when Tinacms gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P
Primary rating from Vendor (github) · only source for this CVE.
CVSS VectorVendor: github
Lifecycle Timeline
3DescriptionCVE.org
Tina is a headless content management system. In tinacms prior to version 3.1.1, tinacms uses the gray-matter package in an insecure way allowing attackers that can control the content of the processed markdown files, e.g., blog posts, to execute arbitrary code. tinacms version 3.1.1, @tinacms/cli version 2.0.4, and @tinacms/graphql version 2.0.3 contain a fix for the issue.
Executive ViewAI
TinaCMS versions prior to 3.1.1 contain a remote code execution vulnerability that allows authenticated users with markdown file access to execute arbitrary code on the server, potentially compromising confidentiality, integrity, and availability of managed content systems. Organizations using TinaCMS for user-contributed content management face immediate risk of server compromise through low-privilege user accounts, particularly where markdown editing is delegated to content contributors or third parties.
Apply vendor patch. If immediate patching is not feasible: restrict markdown file editing permissions to administrators only, disable public or low-privilege user access to content markdown editing, implement network-level access controls limiting markdown processing endpoints, and monitor for suspicious markdown file modifications or server process execution anomalies.
Threat Intelligence Overview
NVD
CVE.org
EPSS
GitHub
VulDB
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Affected Products (CPE)CVE.org
Cross-tenant authorization bypass in TinaCMS self-hosted deployments allows any holder of a legitimate TinaCloud account
Cross-site request forgery in the TinaCMS CLI dev server allows an attacker-controlled web page to write arbitrary files
Broken access control across all four first-party TinaCMS production media adapters (next-tinacms-s3, next-tinacms-dos,
Off-origin preview framing in TinaCMS (tinacms <= 3.13.0 and @tinacms/app <= 2.5.13) lets an unauthenticated attacker wh
Code injection in @tinacms/cli versions up to and including 2.7.0 lets a crafted Git branch name break out of the string
Stored cross-site scripting in TinaCMS's @tinacms/web-components package (all versions up to and including 0.2.0) lets a
Exploit-DB