CVE-2025-66944: databasir · SQL Injection
Affects databasirSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 12:55 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 56% 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:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 4 Mar 2026
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 |
|---|---|---|
GitHubvran-dev/databasirpkg:github/vran-dev/databasirOther 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
Given the absence of official patches, organizations should immediately take the following specific actions: 1) Restrict network access to the vulnerable search API endpoint by implementing IP whitelisting or VPN-only access to limit exposure. 2) Deploy and configure Web Application Firewalls (WAFs) with updated SQL Injection detection rules tailored to the query parameter patterns of the vulnerable API. 3) Conduct thorough input validation and sanitization on all user-supplied data, especially the query parameter, to prevent injection attacks. 4) Monitor logs and network traffic for unusual query patterns or error messages indicative of SQL Injection attempts. 5) Isolate the affected database server from other critical infrastructure to contain potential breaches. 6) Prepare incident response plans specific to SQL Injection exploitation scenarios. 7) Engage with the vendor or community to track patch releases and apply updates promptly once available. 8) Consider temporary migration to alternative database solutions or versions not affected by this vulnerability if feasible. These targeted measures go beyond generic advice by focusing on immediate containment and detection tailored to the vulnerability's characteristics.
Description
SQL Injection vulnerability in vran-dev databaseir v.1.0.7 and before allows a remote attacker to execute arbitrary code via the query parameter in the search API endpoint