# CVE-2026-125749: TaxHacker through 0.8.5 IDOR via Settings Server Actions userId


- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-pwqc-qhg6-97mf

## What is CVE-2026-125749?

CVE-2026-125749 is a low-severity vulnerability in vas3k TaxHacker, published on 10 Nov 2026. 

### Official description

TaxHacker through 0.8.5 contains an insecure direct object reference vulnerability in app/(app)/settings/actions.ts that allows authenticated users to modify other users' data by supplying an arbitrary userId. Attackers can invoke Server Actions like deleteCategoryAction or editFieldAction with a victim's UUID to delete categories, clear transaction assignments, or alter LLM prompts.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-125749?


## How do I fix CVE-2026-125749?

No fix has been published for CVE-2026-125749 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-125749 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-125749 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-125749 and fix it if it is affected.

What it is: CVE-2026-125749 is a low-severity vulnerability in vas3k TaxHacker, published on 10 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-125749 exists.

Affected product: vas3k TaxHacker. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-125749/ (Markdown: https://insights.sbomify.com/CVE-2026-125749/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-125749
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-125749
- OSV: https://osv.dev/vulnerability/CVE-2026-125749

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-125749/
Summaries are generated and may contain mistakes; the official description above is the record.