CVE-2024-44541: inventio-lite · n/a
Affects inventio-liteSource CVE Database V5
Not known to be exploited · public exploit available (Exploit-DB) · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 2.5% chance of exploitation in 30 days – higher than 85% 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:HExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 11 Sep 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
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
Timeline
CVE ID reserved
by mitre
, 21 days before disclosure
CVE published
on cve.org
, t = 0
First Exploit-DB entry (opens in a new tab)
Inventio Lite 4 - SQL Injection
, 219 days after disclosure
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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubevilnapsis/inventio-litepkg:github/evilnapsis/inventio-liteOther threats | Affected
| 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-44541, organizations should immediately assess their use of evilnapsis Inventio Lite and identify affected versions (v4 and earlier). Since no official patches are currently available, temporary mitigations include implementing Web Application Firewalls (WAFs) with rules to detect and block SQL injection attempts targeting the "/?action=processlogin" endpoint and specifically the "username" parameter. Input validation and sanitization should be enforced at the application level to reject or properly escape malicious input. Restricting database user permissions to the minimum necessary can limit the impact of a successful injection. Monitoring logs for unusual database queries or login attempts can help detect exploitation attempts early. Organizations should engage with the vendor for updates and patches and plan for prompt application once released. Additionally, conducting security code reviews and penetration testing focused on injection flaws can uncover similar vulnerabilities. Network segmentation and least privilege principles can reduce the blast radius if exploitation occurs.
Description
evilnapsis Inventio Lite Versions v4 and before is vulnerable to SQL Injection via the "username" parameter in "/?action=processlogin."