nova-tiptap has Unauthenticated Arbitrary File Upload Vulnerability
CVE-2025-54082GHSA-96c2-h667-9fxp
What to do
Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Packagist marshmallow/nova-tiptap
- Affected
- < 5.7.0
- Fixed in
- 5.7.0
Packagist manogi/nova-tiptap
- Affected
- <= 3.2.6
- Fixed in
- no fixed version recorded
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-96c2-h667-9fxp lists affected ranges: Packagist marshmallow/nova-tiptap >=0 =0 <=3.2.6
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 9.3 · 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 · score source
- EPSS
- CVE-2025-54082: 0.94% estimated exploitation activity in the next 30 days; percentile 60.99 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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 • Lack of validation on uploaded files (no MIME/type or extension restrictions) • 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.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-96c2-h667-9fxp
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2025-54082 Advisory: nova-tiptap has Unauthenticated Arbitrary File Upload Vulnerability IDs: CVE-2025-54082, GHSA-96c2-h667-9fxp Record: https://patchnext.com/advisories/cve-2025-54082 (revision 1, source checked 26 Oct 2026, 14:34 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 9.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Partial vendor fix; fixed versions by package: marshmallow/nova-tiptap 5.7.0. A vendor fix does not mean a deployment is fixed. ## Affected components - Packagist marshmallow/nova-tiptap: affected < 5.7.0; fixed in 5.7.0 - Packagist manogi/nova-tiptap: affected <= 3.2.6 ## Suggested inspection (read-only) - Packagist marshmallow/nova-tiptap: check the installed version with your package manager. - Packagist manogi/nova-tiptap: check the installed version with your package manager. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on marshmallow/nova-tiptap, manogi/nova-tiptap. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-96c2-h667-9fxp (GitHub-reviewed advisory GHSA-96c2-h667-9fxp lists affected ranges: Packagist marshmallow/nova-tiptap >=0 =0 <=3.2.6) Commands are suggestions: review each one before running it.
Loading voting…