CVE-2024-44872: mozilo3.0 · A Reflected Cross-site Scripting (XSS)
Affects mozilo3.0Source CVE Database V5
Not known to be exploited · CVSS 6.1 Medium.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% 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:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Sep 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubmozilodaseinsteigercms/mozilo3.0pkg:github/mozilodaseinsteigercms/mozilo3.0Other threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until an official patch is released, organizations should implement several specific mitigations to reduce risk from CVE-2024-44872: 1) Apply strict input validation and output encoding on all user-supplied data to prevent injection of malicious scripts. 2) Use Content Security Policy (CSP) headers to restrict execution of unauthorized scripts in browsers. 3) Deploy or update Web Application Firewalls (WAFs) with rules to detect and block reflected XSS payloads targeting moziloCMS. 4) Educate users and administrators about the risks of clicking untrusted links and phishing attempts. 5) Monitor web server logs for suspicious request patterns indicative of XSS attempts. 6) Isolate or sandbox critical web application components to limit the scope of potential exploitation. 7) Regularly check for moziloCMS updates and apply patches promptly once available. 8) Consider temporary disabling or restricting vulnerable features or input fields if feasible. These targeted actions go beyond generic advice by focusing on the specific nature of reflected XSS and the affected CMS platform.
Description
A reflected cross-site scripting (XSS) vulnerability in moziloCMS v3.0 allows attackers to execute arbitrary code in the context of a user's browser via injecting a crafted payload.