Skip to main content
VulnerabilityPublished

CVE-2026-129540: VoAPI · SQL Injection

Affects VoAPISource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High.

Data as of 16 Nov 2026, 02:04 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.7
CNA (VulnCheck)CVSS 3.18.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 15 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
VoAPIVoAPIAffected
  • >=1.0.0 <=1.2.0
Fixed in–
GitHubVoAPIpkg:github/VoAPIOther threatsAffected
  • >=1.0.0 <=1.2.0
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 access to affected endpoints to trusted users only and monitor for suspicious activity related to token forgery.

Description

VoAPI versions 1.0.0 through 1.2.0 have 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. Exploiting this flaw, attackers can read the HS256 JWT signing secret from the option table and forge manager role tokens to take over management APIs.

References

Community reviews

Loading reviews…