Skip to main content
CVE-2024-51442VulnerabilityPublished

CVE-2024-51442: minidlna · n/a

Affects minidlnaSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
2.3% chance of exploitation in 30 days – higher than 83% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jan 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
GitHubmselbrede/minidlnapkg:github/mselbrede/minidlnaOther threatsAffected
  • <=1.3.3
Fixed in–

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

AI-suggested

To mitigate CVE-2024-51442, organizations should immediately restrict access to the minidlna.conf configuration file to trusted administrators only, preventing unauthorized modification or replacement. Implement strict validation and sanitization of configuration inputs before processing to block injection attempts. Where possible, run Minidlna with the least privileges necessary, ideally in a sandboxed or containerized environment to limit the impact of potential exploitation. Monitor file integrity of configuration files and set up alerts for unexpected changes. Network segmentation can reduce exposure by limiting access to the media server from untrusted networks. Until an official patch is released, consider disabling Minidlna services if not essential or replacing it with alternative media server software with a better security posture. Regularly review and apply security updates from the Minidlna project and maintain an incident response plan for potential exploitation scenarios.

Description

Command Injection in Minidlna version v1.3.3 and before allows an attacker to execute arbitrary OS commands via a specially crafted minidlna.conf configuration file.

References

Community reviews

Loading reviews…