Skip to main content
VulnerabilityPublished Updated

CVE-2024-57639: virtuoso-opensource · SQL Injection

Affects virtuoso-opensourceSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 48% 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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Jan 2025

  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
GitHubopenlink/virtuoso-opensourcepkg:github/openlink/virtuoso-opensourceOther threatsAffected
  • =7.2.11
Fixed in–

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

AI-suggested

Organizations should immediately assess their use of OpenLink Virtuoso OpenSource version 7.2.11 and plan to upgrade to a patched version once available. In the absence of an official patch, implement strict input validation and sanitization at the application layer to prevent malicious SQL queries from reaching the database engine. Employ network-level protections such as Web Application Firewalls (WAFs) configured to detect and block SQL Injection patterns targeting Virtuoso. Restrict network access to the database server to trusted hosts and use network segmentation to minimize exposure. Monitor database logs and network traffic for unusual query patterns indicative of exploitation attempts. Consider deploying rate limiting or query throttling to reduce the impact of potential DoS attempts. Engage with the vendor or community for updates and apply security advisories promptly. Finally, conduct regular security assessments and penetration testing focused on SQL Injection vectors to identify and remediate similar vulnerabilities proactively.

Description

An issue in the dc_elt_size component of openlink virtuoso-opensource v7.2.11 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements.

References

Community reviews

Loading reviews…