Skip to main content
VulnerabilityPublished Updated

CVE-2024-30928: DerbyNet · SQL Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 8.1 High.

Data as of 26 Oct 2026, 13:47 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Apr 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-30928, European organizations should immediately audit all DerbyNet installations to identify affected versions (v9.0 and below). Since no official patches are available, organizations must implement the following specific measures: 1) Conduct a thorough code review focusing on the 'classids' parameter handling in ajax/query.slide.next.inc to ensure proper input validation and use of parameterized queries or prepared statements to prevent SQL injection. 2) Deploy Web Application Firewalls (WAFs) with updated SQL injection detection rules to block malicious payloads targeting this parameter. 3) Restrict access to the vulnerable endpoint by implementing network-level controls such as IP whitelisting or VPN access where feasible. 4) Enable detailed logging and monitoring of database queries and web application logs to detect anomalous activities indicative of exploitation attempts. 5) Educate development and security teams about secure coding practices to prevent similar vulnerabilities in future releases. 6) Engage with DerbyNet vendors or community to track patch releases and apply updates promptly once available. 7) Consider isolating or segmenting affected systems to limit potential lateral movement in case of compromise. These targeted actions go beyond generic advice and address the specific attack vector and affected component.

Description

SQL Injection vulnerability in DerbyNet v9.0 and below allows attackers to execute arbitrary SQL commands via 'classids' Parameter in ajax/query.slide.next.inc

References

Community reviews

Loading reviews…