Skip to main content
VulnerabilityPublished Updated

CVE-2024-57638: 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.7% chance of exploitation in 30 days – higher than 55% 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:N/A:H

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

  1. Immediately restrict network access to the Virtuoso database server by implementing firewall rules or network segmentation to limit exposure to trusted hosts only.
  2. Monitor database logs for unusual or malformed SQL queries that could indicate attempted exploitation.
  3. 4. Implement input validation and sanitization at the application layer to prevent malicious SQL statements from reaching the database. 5. Use Web Application Firewalls (WAFs) or SQL injection detection tools to detect and block suspicious traffic targeting the database. 6. Regularly back up critical data and have an incident response plan to quickly recover from potential DoS incidents. 7. Engage with OpenLink support or community forums to track vulnerability developments and mitigation strategies. 8. Consider deploying Virtuoso behind reverse proxies or VPNs to reduce direct exposure to untrusted networks.

Description

An issue in the dfe_body_copy 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…