Skip to main content
VulnerabilityPublished

CVE-2024-42567: School Management System · SQL Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% 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 20 Aug 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-42567, organizations should immediately audit the affected School Management System for the vulnerable /search.php?action=2 endpoint and the 'sid' parameter. Implement strict input validation and sanitization to reject or properly escape all user-supplied data before database queries. Transition all database interactions to use parameterized queries or prepared statements to prevent injection. If source code access is available, review and refactor the vulnerable commit or module to eliminate direct concatenation of user input in SQL commands. Deploy Web Application Firewalls (WAFs) with SQL injection detection and blocking rules as a compensating control until patches are available. Monitor database logs and application logs for unusual query patterns or error messages indicative of injection attempts. Restrict database user privileges to the minimum necessary to limit damage if exploitation occurs. Educate development teams on secure coding practices to prevent future injection flaws. Coordinate with the software vendor or community to obtain or develop patches and apply them promptly. Finally, conduct penetration testing and vulnerability scanning regularly to detect similar issues proactively.

Description

School Management System commit bae5aa was discovered to contain a SQL injection vulnerability via the sid parameter at /search.php?action=2.

References

Community reviews

Loading reviews…