Skip to main content
CVE-2024-55586VulnerabilityPublished Updated

CVE-2024-55586: database · n/a

Affects databaseSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical : upgrade to 3.2.5 as a priority.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.2.5
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 10 Dec 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 2026-10-26.

What to do

Upgrade nette/database to 3.2.5.

Affected software

ProductAffectedFixed in
Packagistnette/databasepkg:composer/nette/databaseOther threatsAffected
  • <3.2.5
Fixed in
  • 3.2.5

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-55586, organizations should immediately audit all uses of the Nette Database 'where' method to identify instances where untrusted input is passed directly. Developers must implement strict input validation and sanitization to ensure that only safe, expected values are used in filters. Employing parameterized queries or prepared statements wherever possible is critical to prevent SQL injection. If the framework does not support internal parameterization for these cases, consider wrapping or extending the 'where' method to enforce safe query construction. Application-level firewalls or database activity monitoring can help detect and block suspicious SQL injection attempts. Organizations should also monitor for unusual database queries or access patterns indicative of exploitation attempts. Until an official patch or update is available, consider isolating vulnerable applications, restricting database access, or applying compensating controls such as query whitelisting. Finally, maintain up-to-date backups and have an incident response plan ready in case of compromise.

Description

Nette Database through 3.2.4 allows SQL injection in certain situations involving an untrusted filter that is directly passed to the where method. NOTE: the vendor's position is that this is intended behavior.

References

Community reviews

Loading reviews…