CVE-2026-129540
Received Received - Intake

SQL Injection in VoAPI Application

Vulnerability report for CVE-2026-129540, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-16

Last updated on: 2026-11-16

Assigner: VulnCheck

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-16
Last Modified
2026-11-16
Generated
2026-11-16
AI Q&A
2026-11-16
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
VoAPI VoAPI From 1.0.0 (inc) to 1.2.0 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

VoAPI 1.0.0 through 1.2.0 has a SQL injection flaw in its search filter mechanism. Authenticated users can inject malicious SQL code by supplying crafted column names in search parameters on endpoints like GET /api/log. This allows reading the HS256 JWT signing secret from the database and forging a manager role token to gain administrative access.

Detection Guidance

To detect this SQL injection vulnerability in VoAPI, monitor network traffic for suspicious requests to the /api/log endpoint with crafted search parameters. Check for unusual SQL query patterns or errors in logs. Use tools like SQLMap to test for SQL injection by sending payloads such as ' OR 1=1 -- in search filter keys.

Impact Analysis

An attacker could exploit this to extract the JWT secret, forge admin tokens, and gain full control over the VoAPI system. This includes accessing user data, modifying configurations, and maintaining elevated privileges for up to 31 days due to default JWT settings.

Compliance Impact

This vulnerability likely violates compliance requirements such as GDPR (data protection) and HIPAA (health data security) due to unauthorized access to sensitive data and potential data breaches. Full administrative access could lead to unauthorized disclosure of regulated information.

Mitigation Strategies

Immediately upgrade VoAPI to a patched version if available. If not, apply input validation to sanitize search filter keys in the /api/log endpoint. Disable default open registration if enabled. Rotate the HS256 JWT signing secret and invalidate all existing tokens. Restrict database access to prevent unauthorized queries.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-129540. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...