VoAPI 1.0.0 through 1.2.0 contains a sql injection vulnerability that allows authenticated users to inject SQL by
Source GCVE Database
Not known to be exploited · CVSS 8.7 High.
Data as of 16 Nov 2026, 04:19 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 8.7 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 8.8 |
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 15 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| VoAPIVoAPI | Affected
| Fixed in– |
GitHubVoAPIpkg:github/VoAPIOther 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
Until a fix is available, restrict authenticated user privileges to minimize exposure and monitor for suspicious activity related to token forgery attempts.
Description
VoAPI versions 1.0.0 through 1.2.0 contain a SQL injection vulnerability that allows authenticated users to inject SQL via crafted column names in search filter keys on list endpoints such as GET /api/log. Exploitation can lead to reading the HS256 JWT signing secret from the option table, enabling attackers to forge a manager role token and take over management APIs under /api/m/*. This vulnerability is rated high severity with a CVSS score of 8.8.