CVE-2025-61506
Arbitrary File Upload Vulnerability in MediaCrush /upload Endpoint
Publication date: 2026-02-03
Last updated on: 2026-02-11
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| mediacrush | mediacrush | to 1.0.1 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-434 | The product allows the upload or transfer of dangerous file types that are automatically processed within its environment. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2025-61506 is an Unrestricted File Upload vulnerability in MediaCrush versions up to 1.0.1. It exists in the Flask-based /upload endpoint, allowing remote, unauthenticated attackers to upload arbitrary files of any size without restrictions on file size, MIME type, or rate limiting.'}, {'type': 'paragraph', 'content': "The lack of input validation in the upload handler means attackers can upload any file to the server's storage location, which can lead to resource exhaustion and application instability."}] [1]
How can this vulnerability impact me? :
This vulnerability can have several impacts:
- Denial of Service (DoS) by exhausting disk storage and crashing the MediaCrush application.
- Storage abuse, where attackers use the MediaCrush instance as free unlimited storage for malicious or unwanted content.
- Potential increased cloud costs if the storage backend is a cloud service like AWS S3 due to uncontrolled file uploads.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability can be detected by monitoring for unusual or unauthorized file uploads to the /upload endpoint of MediaCrush instances. Since the vulnerability allows uploading arbitrary files of any size without restrictions, signs include rapid disk space consumption, HTTP 500 or 413 errors on uploads, and spikes in Redis and Celery worker resource usage.'}, {'type': 'paragraph', 'content': 'A proof of concept involves uploading large files repeatedly using commands like curl or Python scripts that send data from /dev/zero to the /upload endpoint.'}, {'type': 'paragraph', 'content': 'Example command to test upload behavior (may help detect vulnerability):'}, {'type': 'list_item', 'content': 'curl -X POST -F "file=@/dev/zero" http://<mediacrush-server>/upload'}, {'type': 'paragraph', 'content': 'Monitoring disk usage and application logs for errors such as HTTP 500 or 413 during uploads can also indicate exploitation attempts.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
[{'type': 'paragraph', 'content': 'Immediate mitigation steps include enforcing server-side upload size limits and implementing proper file validation and rate limiting.'}, {'type': 'list_item', 'content': "Configure Flask's MAX_CONTENT_LENGTH setting to limit the maximum allowed upload size."}, {'type': 'list_item', 'content': "Set web server restrictions such as nginx's client_max_body_size directive to restrict upload sizes."}, {'type': 'list_item', 'content': 'Implement file type validation to prevent arbitrary file uploads.'}, {'type': 'list_item', 'content': 'Apply rate limiting to prevent resource exhaustion from repeated uploads.'}, {'type': 'paragraph', 'content': 'Since MediaCrush is unmaintained and no official fix exists, users are advised to fork and patch the software themselves or avoid deploying it.'}] [1]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows remote unauthenticated attackers to upload arbitrary files of any size without restrictions, leading to potential storage abuse and Denial of Service (DoS). This unrestricted file upload can result in the storage of malicious or unauthorized content, which may compromise data integrity and availability.
Such issues can negatively impact compliance with common standards and regulations like GDPR and HIPAA, which require protection of data confidentiality, integrity, and availability. The lack of upload restrictions and validation increases the risk of unauthorized data storage and service disruption, potentially leading to violations of these regulations.
Mitigation involves enforcing server-side upload size limits, proper file validation, and rate limiting to prevent resource exhaustion and unauthorized data uploads, which are necessary steps to maintain compliance.