CVE-2025-54082: marshmallow-packages nova-tiptap · Unrestricted File Upload
Affects marshmallow-packages nova-tiptapSource CVE Database V5
Not known to be exploited · CVSS 8.1 High : upgrade to 5.7.0 soon.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 60% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.7.0
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:UExploitation evidence
Disclosed: evidence found.
CVE published 21 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade marshmallow-packages/nova-tiptap to 5.7.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubmarshmallow-packages/nova-tiptappkg:github/marshmallow-packages/nova-tiptapOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediate upgrade: Organizations should upgrade the nova-tiptap package to version 5.7.0 or later, where the vulnerability is patched. 2. Access control: Until patching is possible, restrict access to the /nova-tiptap/api/file endpoint using web application firewalls (WAFs), IP whitelisting, or network segmentation to limit exposure. 3. Storage configuration: Review and restrict permissions on Laravel disks, especially public and S3 buckets, to prevent public write or execute access. Disable public access on S3 buckets unless absolutely necessary and enforce least privilege policies. 4. Input validation: Implement additional server-side validation for uploaded files, including MIME type checks, file extension whitelisting, and content scanning for malicious payloads. 5. Monitoring and detection: Deploy monitoring to detect unusual file uploads, especially executable files, and anomalous POST requests to the vulnerable endpoint. 6. CSRF token management: Ensure CSRF tokens are rotated and validated properly to reduce the risk of token reuse by attackers. 7. Incident response readiness: Prepare to investigate and remediate potential exploitation attempts, including scanning for web shells or unauthorized files in storage. 8. Developer awareness: Educate development teams on secure file upload practices and the importance of authentication middleware on sensitive endpoints.
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.