CVE-2025-13803

7.3

MediaCrush · MediaCrush

MediaCrush 1.0.0 and 1.0.1 suffer from improper neutralization of HTTP headers in the Host argument, allowing remote attackers to inject scripting syntax via the Header Handler.

Executive summary

A vulnerability in the MediaCrush application allows unauthenticated remote attackers to perform HTTP header manipulation, posing a risk of script injection.

Vulnerability

The flaw exists within the /mediacrush/paths.py file, specifically within the Header Handler component, where the Host argument is not properly sanitized. This allows an unauthenticated attacker to manipulate HTTP headers to introduce scripting syntax into the application environment.

Business impact

The ability to manipulate HTTP headers can lead to cross-site scripting or other injection-based attacks, potentially compromising user sessions or redirecting traffic. With a CVSS score of 7.3, this high-severity vulnerability represents a significant risk to application integrity and data confidentiality. Failure to remediate could allow unauthorized actors to influence how the application processes web requests, leading to potential service disruption or user data exposure.

Remediation

Immediate Action: Review the vendor advisory for available security patches or configuration updates to sanitize the Host header input in the Header Handler component.

Proactive Monitoring: Monitor web server access logs for anomalous HTTP requests containing non-standard or malicious character sequences within the Host header field.

Compensating Controls: Deploy a Web Application Firewall (WAF) configured to inspect and filter incoming HTTP headers, specifically targeting and blocking requests that attempt to inject scripting syntax into the Host header.

Exploitation status

Public Exploit Available: Unknown.

Analyst recommendation

Given the high CVSS score and the potential for remote exploitation, organizations using MediaCrush versions 1.0.0 or 1.0.1 must treat this vulnerability with urgency. Administrators should prioritize identifying instances of this software and applying the necessary vendor-provided patches or mitigations to prevent potential exploitation of the HTTP header injection flaw.

Sources

Originally found and disclosed by lakshay12311 (VulDB User), per the CVE Program record.