CVE-2024-22719: Form Tools · SQL Injection
Source CVE Database V5
Not known to be exploited · CVSS 8.1 High.
Data as of 26 Oct 2026, 11:42 UTC
- 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 11 Apr 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
AI-suggested
Organizations should immediately review their use of Form Tools 3.1.1 and restrict access to the affected search functionality to trusted users only. Implement input validation and parameterized queries or prepared statements to prevent SQL Injection. If vendor patches are unavailable, consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block malicious SQL payloads targeting the 'keyword' parameter. Conduct thorough code audits and penetration testing to identify and remediate similar injection points. Additionally, monitor database logs for unusual query patterns and enforce the principle of least privilege on database accounts used by Form Tools. Regular backups and incident response plans should be updated to prepare for potential exploitation scenarios.
Description
SQL Injection vulnerability in Form Tools 3.1.1 allows attackers to run arbitrary SQL commands via the 'keyword' when searching for a client.