Skip to main content
VulnerabilityPublished

CVE-2024-44871: mozilo3.0 · An Arbitrary File Upload

Affects mozilo3.0Source CVE Database V5

0

Public exploit available (Exploit-DB) · 16% EPSS · CVSS 7.2 High.

Data as of 26 Oct 2026, 14:05 UTC

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

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 10 Sep 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

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

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by MITRE Corporation

    , 20 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. First Exploit-DB entry (opens in a new tab)

    MoziloCMS 3.0 - Remote Code Execution (RCE)

    , 198 days after disclosure

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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubmozilodaseinsteigercms/mozilo3.0pkg:github/mozilodaseinsteigercms/mozilo3.0Other threatsAffected
  • =3.0
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. Immediately restrict access to the /admin/index.php interface by IP whitelisting or VPN-only access to limit exposure.
  2. Implement strict file upload validation on the server side, including checking file types, MIME types, and file contents to prevent dangerous files from being accepted.
  3. Employ web application firewalls (WAFs) with rules to detect and block suspicious file upload attempts targeting this endpoint.
  4. Monitor server logs and file system changes for unusual activity indicative of exploitation attempts.
  5. Enforce strong authentication and multi-factor authentication for administrative accounts to reduce the risk of credential compromise.
  6. Regularly back up website data and configurations to enable recovery in case of compromise.
  7. Stay alert for official patches or updates from moziloCMS and apply them promptly once available.
  8. Consider isolating the CMS environment in a container or sandbox to limit the blast radius of a potential compromise.

Description

An arbitrary file upload vulnerability in the component /admin/index.php of moziloCMS v3.0 allows attackers to execute arbitrary code via uploading a crafted file.

References

Community reviews

Loading reviews…