Skip to main content
VulnerabilityPublished

CVE-2025-13803: MediaCrush 1.0.0/1.0.1 · CWE-644

Source GCVE Database

0
Compare
Authoritative record:CVE-2025-13803· Medium 6.9

Not known to be exploited · CVSS 6.9 Medium.

Data as of 20 Nov 2026, 00:57 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 19 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
PyPImediacrushpkg:pypi/mediacrushOther threatsAffected
  • =1.0.0
  • =1.0.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should monitor vendor advisories for updates and apply any official fixes once released. In the meantime, consider restricting or validating Host header inputs if possible to mitigate potential exploitation.

Description

A vulnerability in MediaCrush versions 1.0.0 and 1.0.1 involves improper neutralization of HTTP headers due to manipulation of the Host argument in the Header Handler component. This flaw allows remote attackers to exploit scripting syntax issues in HTTP headers, potentially leading to limited confidentiality, integrity, and availability impacts.

References

Community reviews

Loading reviews…