Skip to main content
VulnerabilityPublished Updated

CVE-2024-33403: A 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-33403, organizations should immediately implement strict input validation and sanitization on the event_id parameter and any other user-supplied inputs to prevent SQL injection. Employing parameterized queries or prepared statements in the application code is critical to eliminate direct injection risks. Deploying a Web Application Firewall (WAF) with rules tailored to detect and block SQL injection attempts can provide an additional layer of defense. Network segmentation and limiting external access to the affected web application can reduce exposure. Monitoring database logs and application logs for unusual query patterns or errors may help detect attempted exploitation. Until an official patch is released, consider isolating the vulnerable system or restricting access to trusted IP addresses. Conduct regular security audits and penetration testing focused on injection flaws. Educate developers and administrators on secure coding practices and the importance of input validation. Finally, maintain up-to-date backups of critical data to enable recovery in case of compromise.

Description

A SQL injection vulnerability in /model/get_events.php in campcodes Complete Web-Based School Management System 1.0 allows attacker to execute arbitrary SQL commands via the event_id parameter.

References

Community reviews

Loading reviews…