# CVE-2024-45391: Tina search token leak via lock file in TinaCMS

> Attackers can read search tokens from lock files in TinaCMS CLI, potentially bypassing search security controls.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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:** 3 Sep 2024
- **Updated:** 3 Sep 2024
- **Also known as:** GHSA-4qrm-9h4r-v2fx

## What is CVE-2024-45391?

CVE-2024-45391 is a high-severity vulnerability in tinacms, published on 3 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Tina is an open-source content management system (CMS). Sites building with Tina CMS's command line interface (CLI) prior to version 1.6.2 that use a search token may be vulnerable to the search token being leaked via lock file (tina-lock.json). Administrators of Tina-enabled websites with search setup should rotate their key immediately. This issue has been patched in @tinacms/cli version 1.6.2. Upgrading and rotating the search token is required for the proper fix.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2024-45391?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@tinacms/cli` | npm | All versions | 1.6.2 |
| `@tinacms/cli` | npm | All versions | 1.6.2 |

Products: Ssw Tinacms\/Cli.

## How do I fix CVE-2024-45391?

Upgrade @tinacms/cli to 1.6.2 or later.

## Is CVE-2024-45391 being exploited?

There is no known exploitation of CVE-2024-45391 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-2023-25164](https://insights.sbomify.com/CVE-2023-25164/): Sensitive Information leak via Script File in TinaCMS (high 8.6)
- [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-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-2024-45391 and fix it if it is affected.

What it is: CVE-2024-45391 is a high-severity vulnerability in tinacms, published on 3 Sep 2024. 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-2024-45391 in the wild and no public exploit code.

Affected packages and fixed versions:
- @tinacms/cli (npm): affected all versions; fixed in 1.6.2
- @tinacms/cli (npm): affected all versions; fixed in 1.6.2

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-2024-45391/ (Markdown: https://insights.sbomify.com/CVE-2024-45391/index.md)
```

## Sources

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

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