Skip to main content
VulnerabilityPublished Updated

CVE-2024-33409: SQL Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 53% 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 6 May 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

AI-suggested

To mitigate CVE-2024-33409, organizations should immediately implement the following measures: 1) Apply strict input validation and sanitization on the 'name' parameter to reject or neutralize malicious SQL syntax. 2) Refactor the application code to use parameterized queries or prepared statements instead of dynamic SQL concatenation. 3) Employ web application firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting the vulnerable endpoint. 4) Monitor logs for unusual database query patterns or repeated failed requests to index.php with suspicious 'name' parameter values. 5) Restrict database user permissions to the minimum necessary to limit the impact of a potential injection. 6) Engage with the software vendor or community to obtain patches or updates addressing this vulnerability as soon as they become available. 7) Conduct regular security assessments and penetration testing focused on injection flaws. 8) Educate developers on secure coding practices to prevent similar vulnerabilities in future releases.

Description

SQL injection vulnerability in index.php in campcodes Complete Web-Based School Management System 1.0 allows attacker to execute arbitrary SQL commands via the name parameter.

References

Community reviews

Loading reviews…