# CVE-2025-54082: nova-tiptap has an Unauthenticated Arbitrary File Upload Vulnerability

> Unauthenticated attackers can upload arbitrary files to any configured disk, potentially leading to remote code execution or malicious file distribution.

- **Severity:** High 8.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Jul 2025
- **Updated:** 21 Jul 2025
- **Also known as:** GHSA-96c2-h667-9fxp

## What is CVE-2025-54082?

CVE-2025-54082 is a high-severity vulnerability in marshmallow-packages nova-tiptap, published on 21 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

marshmallow-packages/nova-tiptap is a rich text editor for Laravel Nova based on tiptap. Prior to 5.7.0, a vulnerability was discovered in the marshmallow-packages/nova-tiptap Laravel Nova package that allows unauthenticated users to upload arbitrary files to any Laravel disk configured in the application. The vulnerability is due to missing authentication middleware (Nova and Nova.Auth) on the /nova-tiptap/api/file upload endpoint, the lack of validation on uploaded files (no MIME/type or extension restrictions), and the ability for an attacker to choose the disk parameter dynamically. This means an attacker can craft a custom form and send a POST request to /nova-tiptap/api/file, supplying a valid CSRF token, and upload executable or malicious files (e.g., .php, binaries) to public disks such as local, public, or s3. If a publicly accessible storage path is used (e.g. S3 with public access, or Laravel’s public disk), the attacker may gain the ability to execute or distribute arbitrary files — amounting to a potential Remote Code Execution (RCE) vector in some environments. This vulnerability was fixed in 5.7.0.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2025-54082?

4 open source packages ship an affected version, including manogi/nova-tiptap and marshmallow/nova-tiptap.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `manogi/nova-tiptap` | Packagist | All versions to 3.2.6 | None |
| `manogi/nova-tiptap` | Packagist | All versions to 3.2.6 | None |
| `marshmallow/nova-tiptap` | Packagist | All versions | 5.7.0 |
| `marshmallow/nova-tiptap` | Packagist | All versions | 5.7.0 |

## How do I fix CVE-2025-54082?

Upgrade to a fixed version.

## Is CVE-2025-54082 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-54082 and fix it if it is affected.

What it is: CVE-2025-54082 is a high-severity vulnerability in marshmallow-packages nova-tiptap, published on 21 Jul 2025. 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-2025-54082 in the wild and no public exploit code.

Affected packages and fixed versions:
- manogi/nova-tiptap (Packagist): affected all versions up to 3.2.6; no fix listed
- manogi/nova-tiptap (Packagist): affected all versions up to 3.2.6; no fix listed
- marshmallow/nova-tiptap (Packagist): affected all versions; fixed in 5.7.0
- marshmallow/nova-tiptap (Packagist): affected all versions; fixed in 5.7.0

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

## Sources

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

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