Skip to main content
CVE-2024-37765VulnerabilityPublished Updated

CVE-2024-37765: cve-2024-37765 · n/a

Affects cve-2024-37765Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 08:30 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Jul 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
GitHubatreb92/cve-2024-37765pkg:github/atreb92/cve-2024-37765Other threatsAffected
  • <=19
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-37765, organizations should implement the following specific measures: 1) Restrict user privileges strictly to the minimum necessary, especially for accounts with access to the user account settings page. 2) Monitor application and database logs for unusual query patterns or repeated failed attempts indicative of SQL injection probing. 3) Employ Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection payloads targeting the user account settings functionality. 4) Enforce strong authentication and session management to reduce the risk of credential compromise. 5) Conduct internal code reviews and penetration testing focused on the user account settings page to identify and remediate injection points. 6) Prepare for rapid patch deployment once an official fix is released by the vendor. 7) Consider isolating the Machform application environment to limit lateral movement in case of compromise. 8) Educate users about the importance of safeguarding credentials to prevent unauthorized access. These steps go beyond generic advice by focusing on privilege restriction, monitoring, and proactive detection tailored to this vulnerability's characteristics.

Description

Machform up to version 19 is affected by an authenticated Blind SQL injection in the user account settings page.

References

Community reviews

Loading reviews…