Skip to main content
VulnerabilityPublished Updated

CVE-2024-41618: web-money-manager-ex · SQL Injection

Affects web-money-manager-exSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

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 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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 24 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

Affected software

ProductAffectedFixed in
GitHubmoneymanagerex/web-money-manager-expkg:github/moneymanagerex/web-money-manager-exOther threatsAffected
  • =1.2.2
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-41618, organizations should immediately implement the following measures: 1) Apply any available patches or updates from the Money Manager EX WebApp developers as soon as they are released. 2) If patches are not yet available, restrict network access to the vulnerable web application, limiting it to trusted internal users only. 3) Implement Web Application Firewall (WAF) rules to detect and block SQL Injection attack patterns targeting the TrDeleteArr parameter. 4) Conduct code review and refactor the transaction_delete_group function to use parameterized queries or prepared statements, ensuring proper input sanitization and escaping. 5) Employ database least privilege principles, ensuring the application database user has minimal permissions to limit the impact of a successful injection. 6) Monitor application logs and database logs for suspicious queries or anomalies indicative of exploitation attempts. 7) Educate developers and administrators about secure coding practices to prevent similar vulnerabilities in the future. 8) Consider isolating the vulnerable service in a segmented network zone to reduce potential lateral movement if compromised.

Description

Money Manager EX WebApp (web-money-manager-ex) 1.2.2 is vulnerable to SQL Injection in the `transaction_delete_group` function. The vulnerability is due to improper sanitization of user input in the `TrDeleteArr` parameter, which is directly incorporated into an SQL query.

References

Community reviews

Loading reviews…