Skip to main content
CVE-2024-33410VulnerabilityPublished Updated

CVE-2024-33410: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 8.1 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/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 2026-10-26.

What to do

AI-suggested

To mitigate CVE-2024-33410, organizations should immediately implement strict input validation and sanitization on the id parameter to prevent injection of malicious SQL code. Employing prepared statements with parameterized queries is essential to eliminate direct concatenation of user input into SQL commands. If possible, apply web application firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting this endpoint. Conduct thorough code reviews and security testing of all database interaction points within the application. Monitor database logs and application behavior for unusual queries or access patterns indicative of exploitation attempts. Until an official patch is released, consider isolating or restricting access to the vulnerable endpoint and applying network-level controls to limit exposure. Educate developers and administrators on secure coding practices and maintain an incident response plan tailored for database compromise scenarios.

Description

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

References

Community reviews

Loading reviews…