# CVE-2023-25164: Sensitive Information leak via Script File in TinaCMS

> Sensitive environment variables are leaked in plaintext to the index.js file, exposing credentials to attackers.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Feb 2023
- **Updated:** 10 Mar 2025
- **Also known as:** GHSA-pc2q-jcxq-rjrr

## What is CVE-2023-25164?

CVE-2023-25164 is a high-severity vulnerability in tinacms, published on 8 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Tinacms is a Git-backed headless content management system with support for visual editing. Sites being built with @tinacms/cli >= 1.0.0 && < 1.0.9 which store sensitive values in the process.env variable are impacted. These values will be added in plaintext to the index.js file. If you're on a version prior to 1.0.0 this vulnerability does not affect you. If you are affected and your Tina-enabled website has sensitive credentials stored as environment variables (eg. Algolia API keys) you should rotate those keys immediately. This issue has been patched in @tinacms/cli@1.0.9. Users are advised to upgrade. There are no known workarounds for this issue.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2023-25164?

2 open source packages ship an affected version, including @tinacms/cli. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@tinacms/cli` | npm | From 1.0.0 | 1.0.9 |
| `@tinacms/cli` | npm | From 1.0.0 | 1.0.9 |

Products: Ssw Tinacms\/Cli.

## How do I fix CVE-2023-25164?

Upgrade @tinacms/cli to 1.0.9 or later.

## Is CVE-2023-25164 being exploited?

There is no known exploitation of CVE-2023-25164 in the wild and no public exploit code.

## Other vulnerabilities in tinacms

- [CVE-2026-28792](https://insights.sbomify.com/CVE-2026-28792/): Cross-Origin File Exfiltration via CORS Misconfiguration + Path Traversal in TinaCMS (critical 9.7)
- [CVE-2026-28793](https://insights.sbomify.com/CVE-2026-28793/): Path Traversal Leading to Arbitrary File Read, Write and Delete in TinaCMS (high 8.4)
- [CVE-2024-45391](https://insights.sbomify.com/CVE-2024-45391/): Tina search token leak via lock file in TinaCMS (high 7.5)
- [CVE-2026-28791](https://insights.sbomify.com/CVE-2026-28791/): Path Traversal in Media Upload Handle in Tina (high 7.4)
- [CVE-2026-34603](https://insights.sbomify.com/CVE-2026-34603/): @tinacms/graphql's Media Endpoints Can Escape the Media Root via Symlinks or Junctions (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-25164 and fix it if it is affected.

What it is: CVE-2023-25164 is a high-severity vulnerability in tinacms, published on 8 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-25164 in the wild and no public exploit code.

Affected packages and fixed versions:
- @tinacms/cli (npm): affected from 1.0.0; fixed in 1.0.9
- @tinacms/cli (npm): affected from 1.0.0; fixed in 1.0.9

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-25164/ (Markdown: https://insights.sbomify.com/CVE-2023-25164/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-25164
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-25164
- OSV: https://osv.dev/vulnerability/CVE-2023-25164

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-25164/
Summaries are generated and may contain mistakes; the official description above is the record.