Technical impact
VoAPI versions 1.0.0 through 1.2.0 allow an authenticated user to inject arbitrary SQL by supplying crafted column names as search filter keys on list endpoints such as GET /api/log. The injected queries can extract sensitive data from the database, most notably the HS256 JWT signing secret stored in the options table. By learning this secret the attacker can forge a manager‑level JWT and gain unrestricted access to the /api/m/* management API. The resulting compromise provides full administrative control over the VoAPI instance.
Affected Systems
The vulnerability is present in the Open‑Source VoAPI product, specifically in versions 1.0.0 up to and including 1.2.0. All installations running any of these releases are affected.
Risk and Exploitability
The CVSS score of 8.7 indicates a high severity impact. EPSS information is not available, but the lack of listing in CISA KEV does not mitigate its potential for exploitation. The exploitation requires that the attacker have an authenticated account and the ability to invoke GET list endpoints with arbitrary filter keys, implying that accidental exposure would likely occur in environments with broad API access. Once exploited, the attacker can read the signing secret and create a privileged JWT, effectively taking over the system.