CVE-2024-41344: Ecommerce-CodeIgniter-Bootstrap · Cross-Site Request Forgery (CSRF)
Affects Ecommerce-CodeIgniter-BootstrapSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 15 Oct 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubkirilkirkov/Ecommerce-CodeIgniter-Bootstrappkg:github/kirilkirkov/Ecommerce-CodeIgniter-BootstrapOther 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-41344, organizations should implement the following specific measures: 1) Immediately audit all web applications running CodeIgniter 3.1.13 to identify affected instances, particularly those exposing administrative interfaces. 2) Implement or enforce CSRF tokens on all state-changing requests, especially those related to authentication and password changes, to prevent unauthorized requests. 3) Restrict access to administrative endpoints using network-level controls such as IP whitelisting, VPNs, or web application firewalls (WAFs) configured to detect and block suspicious CSRF patterns. 4) Monitor logs for unusual password change activities or multiple failed login attempts that could indicate exploitation attempts. 5) If possible, upgrade to a newer, patched version of CodeIgniter once available or apply community-developed patches or workarounds that address CSRF protections. 6) Educate developers and administrators on secure coding practices related to CSRF and session management. 7) Employ multi-factor authentication (MFA) for administrator accounts to add an additional layer of security against credential compromise. 8) Conduct regular security assessments and penetration testing focusing on CSRF and privilege escalation vectors.
Description
A Cross-Site Request Forgery (CSRF) in Codeigniter 3.1.13 allows attackers to arbitrarily change the Administrator password and escalate privileges.