Skip to main content
VulnerabilityPublished Updated

CVE-2024-33485: 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 14 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

Immediate mitigation steps include conducting a thorough code audit of the login.php component and any other input-handling modules to identify and remediate SQL Injection flaws. Developers should implement parameterized queries or prepared statements using MySQLi or PDO to prevent injection. Input validation and sanitization must be enforced rigorously on all user-supplied data. Until official patches are released, organizations should consider deploying Web Application Firewalls (WAFs) with SQL Injection detection rules tailored to the CASAP system's traffic patterns. Monitoring and logging of database queries and login attempts should be enhanced to detect suspicious activity. Network segmentation can limit exposure of the enrollment system to trusted internal users only. Additionally, organizations should prepare incident response plans specific to potential data breaches involving enrollment data. Regular backups and integrity checks of enrollment databases will aid in recovery if an attack occurs. Coordination with CASAP vendors or developers for timely patch releases is critical.

Description

SQL Injection vulnerability in CASAP Automated Enrollment System using PHP/MySQLi with Source Code V1.0 allows a remote attacker to obtain sensitive information via a crafted payload to the login.php component

References

Community reviews

Loading reviews…