Skip to main content
VulnerabilityPublished Updated

CVE-2024-37846: Code Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · fixed in 5.2.0 : patch affected systems as a priority.

Data as of 26 Oct 2026, 09:15 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Oct 2024

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

What to do

AI-suggested

To mitigate CVE-2024-37846, organizations should immediately restrict access to the Platform Management Edit page by implementing network segmentation and access control lists (ACLs) to limit exposure to trusted administrators only. Deploy web application firewalls (WAFs) with rules specifically designed to detect and block client-side template injection patterns. Monitor network traffic and system logs for unusual activity indicative of exploitation attempts, such as unexpected template code or anomalous requests to the management interface. If you cannot patch yet, consider disabling or restricting the vulnerable management functionality if operationally feasible. Conduct thorough security assessments and penetration testing focused on client-side injection vectors. Educate administrators about the risks and signs of exploitation. Additionally, maintain up-to-date backups and incident response plans to quickly recover from potential compromises.

Description

MangoOS before 5.2.0 was discovered to contain a Client-Side Template Injection (CSTI) vulnerability via the Platform Management Edit page.

References

Community reviews

Loading reviews…