CVE-2026-129540

VoAPI 1.0.0 through 1.2.0 SQL Injection via search Filter Key

Published Nov 16, 2026 CVSS 4.0 · 8.7 High EPSS n/a KEV · Not listed
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.

Analysis

AI-generated

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.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to the latest VoAPI release that patches the SQL injection flaw.
  • Prevent injection by sanitizing the search filter key input; ensure only whitelisted column names are accepted.
  • Rotate the HS256 JWT signing secret to invalidate any tokens that may have been forged.
  • Monitor API traffic for unusual SQL queries and enforce least privilege on API credentials.

Generated by OpenCVE AI on November 16, 2026 at 03:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
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.
Title VoAPI 1.0.0 through 1.2.0 SQL Injection via search Filter Key
Weaknesses CWE-89
References
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 8.7, 'vector': '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'}

Subscriptions

No data.

Weaknesses
  • CWE-89

    Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 16, 2026, 1:50 AM
Reserved
Nov 16, 2026, 12:05 AM
Status
Received
Published
Nov 16, 2026, 2:17 AM
Modified
Nov 16, 2026, 2:17 AM