Skip to main content
VulnerabilityPublished Updated

CVE-2024-27709: Eskooly Web Product v · SQL Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
9.8Critical
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:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Jul 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 should focus on implementing strict input validation and sanitization for the 'searchby' and 'id' parameters in the affected components. Employing parameterized queries or prepared statements in the backend code is critical to prevent SQL Injection. Deploying a Web Application Firewall (WAF) with rules to detect and block SQL Injection attempts can provide a temporary protective layer. Organizations should conduct thorough code reviews and penetration testing on Eskooly installations to identify and remediate similar injection points. Monitoring logs for unusual database queries or access patterns can help detect exploitation attempts early. Until an official patch is released, consider isolating the affected web components or restricting access to trusted networks. Regular backups and incident response plans should be updated to prepare for potential exploitation scenarios. Engaging with Eskooly vendors or community for updates and patches is recommended.

Description

SQL Injection vulnerability in Eskooly Web Product v.3.0 allows a remote attacker to execute arbitrary code via the searchby parameter of the allstudents.php component and the id parameter of the requestmanager.php component.

References

Community reviews

Loading reviews…