Skip to main content
VulnerabilityPublished Updated

CVE-2024-57652: 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, 12:54 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

Given the absence of an official patch, organizations should implement the following specific mitigations: 1) Restrict network access to the Virtuoso service by using firewalls or network segmentation to limit exposure to trusted hosts only. 2) Employ Web Application Firewalls (WAFs) or SQL query monitoring tools to detect and block anomalous or malformed SQL statements targeting the numeric_to_dv component. 3) Monitor logs closely for unusual query patterns or repeated failed attempts that may indicate exploitation attempts. 4) If possible, upgrade to a later version of Virtuoso once a patch addressing this vulnerability is released. 5) Consider deploying rate limiting or connection throttling to reduce the impact of automated attack attempts. 6) Conduct internal audits of SQL query usage to identify and remediate any unsafe query constructions that could be exploited. 7) Maintain an incident response plan to quickly isolate and recover affected services in case of a DoS event.

Description

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