Skip to main content
VulnerabilityPublished Updated

CVE-2024-30923: derbynet · SQL Injection

Affects derbynetSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.3% chance of exploitation in 30 days – higher than 71% 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 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

Affected software

ProductAffectedFixed in
Mavencom.derbynet/derbynetpkg:maven/com.derbynet/derbynetOther threatsAffected
  • <=9.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Given the lack of available patches, European organizations should implement immediate compensating controls. These include restricting network access to DerbyNet servers by using firewalls and network segmentation to limit exposure to trusted internal networks only. Employ web application firewalls (WAFs) with custom rules to detect and block suspicious SQL injection patterns, especially targeting the 'where' clause in document rendering requests. Conduct thorough input validation and sanitization on any user-supplied data interfacing with DerbyNet components. Monitor logs for anomalous database queries or unusual application behavior indicative of injection attempts. Consider deploying intrusion detection/prevention systems (IDS/IPS) tuned for SQL injection signatures. Organizations should also prepare incident response plans specific to this vulnerability and prioritize patch management once updates become available. Engaging with DerbyNet vendors for timely security advisories and patches is critical. Finally, educating developers and administrators on secure coding and configuration practices related to SQL injection can reduce future risks.

Description

SQL Injection vulnerability in DerbyNet v9.0 and below allows a remote attacker to execute arbitrary code via the where Clause in Racer Document Rendering

References

Community reviews

Loading reviews…