CVE
VoAPI privilege escalation via SQL injection in search filters
Affects VoAPI 1.0.0 through 1.2.0. The checked facts name no fixed version and no vendor severity rating.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
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
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected versions are VoAPI 1.0.0 through 1.2.0. With the default configuration, the attacker can register an account to get the authenticated access needed. If registration or check-in is closed, a normal account and one log row are required.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.27% · 20th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 23/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
VoAPI versions 1.0.0 through 1.2.0 contain a SQL injection flaw in the search filter keys on list endpoints such as GET /api/log. Remotely, a user with a low-privilege login can exploit it to read the JWT signing secret and forge a manager token, gaining control of the management API.
Original 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.
Who should check
Anyone running VoAPI 1.0.0 through 1.2.0, including the official Docker compose deployment, where users can register accounts.
“Affected versions: 1.0.0 to 1.2.0”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.7/10CVSS 8.7, total technical impact per CISA
- No patch5/5No patch listed yet
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
- Would score about 30 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected versions are VoAPI 1.0.0 through 1.2.0. With the default configuration, the attacker can register an account to get the authenticated access needed. If registration or check-in is closed, a normal account and one log row are required.Workaround: The checked facts name no workaround or fix. The advisory's conditions depend on whether registration or check-in is open, so that setting is the one to review while waiting for a fix.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129540 (VoAPI 1.0.0 through 1.2.0 SQL Injection via search Filter Key), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129540 (entry last updated 2026-11-16):
Affected:
- VoAPI VoAPI: from 1.0.0, through 1.2.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Affected versions are VoAPI 1.0.0 through 1.2.0. (source: https://vul.yulun.ac.cn/20261115/voapi/)
- With the default configuration, the attacker can register an account to get the authenticated access needed. (source: https://vul.yulun.ac.cn/20261115/voapi/)
- If registration or check-in is closed, a normal account and one log row are required. (source: https://vul.yulun.ac.cn/20261115/voapi/)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-129540 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129540 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/VoAPI/VoAPI/issues/78
- https://vul.yulun.ac.cn/20261115/voapi/
- https://www.vulncheck.com/advisories/voapi-1.0.0-through-1.2.0-sql-injection-via-search-filter-key
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129540
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129540"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- VoAPI VoAPI
From 1.0.0 · through 1.2.0
Evidence 5
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129540
Is CVE-2026-129540 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An authenticated user can read the JWT signing secret from the option table and use it to forge a manager role token. That token lets them take over the /api/m/* management API.Source: vul.yulun.ac.cn, vulncheck.com
Which versions are affected by CVE-2026-129540?
VoAPI: from 1.0.0 through 1.2.0.Source: cve.now feed data
Am I affected, and how do I check?
VoAPI versions 1.0.0 through 1.2.0 are affected. With the default configuration, an attacker can register an account to obtain the needed authenticated access. If registration or check-in is closed, a normal account and one log row are required. Compare the installed VoAPI version against that range.Source: vul.yulun.ac.cn, vulncheck.com
How do I fix CVE-2026-129540?
The checked facts name no fixed version or patch, so no upgrade target can be given. Check the vendor's advisory for a fixed release before relying on any version.Source: vul.yulun.ac.cn, vulncheck.com
What if there's no patch?
The checked facts name no workaround or fix. The advisory's conditions depend on whether registration or check-in is open, so that setting is the one to review while waiting for a fix.Source: vul.yulun.ac.cn, vulncheck.com