CVE-2026-129540 in VoAPI
Summary
by MITRE • 11/16/2026
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.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 11/16/2026
The vulnerability identified in VoAPI versions 1.0.0 through 1.2.0 represents a critical SQL injection flaw that exploits improper validation of user-supplied input within search filter parameters. Specifically, when authenticated users interact with list endpoints such as GET /api/log, the application processes column names provided as keys for filtering operations without adequate sanitization or parameterization. This architectural oversight allows an attacker to inject arbitrary SQL commands by manipulating these column name fields. Unlike traditional injection vectors that target value inputs like passwords or search strings, this vulnerability targets structural elements of the query itself, enabling more complex and potentially damaging exploitation scenarios because it bypasses standard input validation checks typically applied to data values rather than schema definitions.
The operational impact of this flaw is severe due to its direct correlation with authentication mechanisms and administrative access controls. By leveraging the SQL injection capability, an attacker can execute queries against internal database tables that are not intended for public or user-level access. A primary consequence highlighted in reports is the ability to extract sensitive configuration data from the option table, specifically the HS256 JWT signing secret. The disclosure of this cryptographic key effectively breaks the integrity and authenticity guarantees provided by JSON Web Tokens used throughout the application. Once an attacker possesses the signing secret, they can forge valid authentication tokens with arbitrary roles, including elevated privileges such as manager or administrator access. This allows unauthorized entities to take over management APIs located under /api/m/*, granting them full control over critical system functions and data manipulation capabilities that should be restricted to legitimate administrators only.
From a classification perspective, this vulnerability aligns closely with CWE-89 Improper Neutralization of Special Elements used in an SQL Command commonly known as SQL Injection. The specific technique employed here falls under the sub-category of second-order or structural injection where user input influences query structure rather than just data values. In terms of offensive security frameworks such as MITRE ATT&CK, this exploitation path maps to T1059 Command and Scripting Interpreter via database commands for initial access and privilege escalation, followed by T1528 Steal Application Access Token when the JWT secret is exfiltrated. The subsequent forgery of tokens corresponds to T1606 Forging Web Tokens, which facilitates unauthorized lateral movement within the application's logical architecture.
Mitigation strategies must address both immediate remediation and long-term architectural improvements. Developers should immediately patch VoAPI to versions later than 1.2.0 where this issue has been resolved by implementing strict allow-lists for column names used in search filters rather than accepting arbitrary input strings. All database interactions involving user-supplied data, including structural elements like table or column identifiers, must utilize parameterized queries or prepared statements wherever possible, although standard parametrization does not always support dynamic schema references requiring careful implementation of whitelisting logic instead. Additionally, the JWT signing secret should be rotated immediately upon detection of any potential compromise to invalidate forged tokens issued by attackers during the window of vulnerability exposure. Security monitoring should also be enhanced to detect anomalous query patterns originating from authenticated sessions that attempt to access sensitive configuration tables or exhibit characteristics typical of SQL injection payloads in non-standard fields.