CVE-2026-129540
VoAPI 1.0.0 through 1.2.0 SQL Injection via search Filter Key
Description
VoAPI 1.0.0 through 1.2.0 contains a sql injection vulnerability that allows authenticated users to inject SQL by supplying crafted column names as search[...] filter keys on list endpoints such as GET /api/log. Attackers can read the HS256 JWT signing secret from the option table and forge a manager role token to take over the /api/m/* management API.
INFO
Published Date :
Nov. 16, 2026, 1:50 a.m.
Last Modified :
Nov. 16, 2026, 1:50 a.m.
Remotely Exploit :
Yes !
Source :
VulnCheck
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | HIGH | 83251b91-4cc7-4094-a5c7-464a1b83ea10 | ||||
| CVSS 3.1 | HIGH | MITRE-CVE | ||||
| CVSS 4.0 | HIGH | 83251b91-4cc7-4094-a5c7-464a1b83ea10 |
Solution
- Update VoAPI to version 1.2.1 or later.
- Sanitize user-supplied column names in search filters.
- Avoid storing sensitive data in database options.
- Implement robust JWT validation and authorization checks.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-129540 vulnerability anywhere in the article.