Skip to main content
VulnerabilityPublished

CVE-2024-45186: FileSender · Code Injection

Source CVE Database V5

0

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

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.49
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 2 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-45186, organizations should immediately upgrade FileSender to version 2.49 or later once available, as this will contain the necessary patches to fix the SSTI vulnerability. If you cannot patch yet, administrators should restrict access to FileSender instances by implementing network-level controls such as IP whitelisting, VPN-only access, or firewall rules to limit exposure. Additionally, input validation and sanitization should be enforced on all user-supplied data that interacts with template engines to prevent injection of malicious code. Employing template sandboxing or switching to safer templating engines can reduce the risk of SSTI. Monitoring logs for unusual template processing errors or suspicious requests can help detect attempted exploitation. Regularly auditing and rotating credentials stored on the server will limit damage if credentials are compromised. Finally, organizations should maintain an incident response plan to quickly address any signs of compromise related to this vulnerability.

Description

FileSender before 2.49 allows server-side template injection (SSTI) for retrieving credentials.

References

Community reviews

Loading reviews…