CVE-2024-57640: virtuoso-opensource · SQL Injection
Affects virtuoso-opensourceSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% 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:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 14 Jan 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
GitHubopenlink/virtuoso-opensourcepkg:github/openlink/virtuoso-opensourceOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2024-57640, organizations should first verify if they are running OpenLink Virtuoso OpenSource version 7.2.11 and plan to upgrade to a patched version once available. In the absence of an official patch, immediate mitigations include restricting network access to the Virtuoso database server using firewalls or VPNs to limit exposure to trusted users only. Implement strict input validation and sanitization on all SQL queries and interfaces interacting with Virtuoso to prevent injection of malicious SQL statements. Employ database activity monitoring and anomaly detection to identify unusual query patterns indicative of exploitation attempts. Disable or limit the use of the vulnerable dc_add_int component if possible, or isolate it from untrusted inputs. Regularly audit and review database logs for signs of attempted or successful exploitation. Additionally, consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block SQL injection attempts targeting Virtuoso. Finally, maintain up-to-date backups and have an incident response plan ready to restore service quickly in case of a successful attack.
Description
An issue in the dc_add_int component of openlink virtuoso-opensource v7.2.11 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements.