# CVE-2026-125365: DollarDollar through 4.4 Missing Authorization in /add_expense Balance Tampering


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-cffh-jr3f-2pq9

## What is CVE-2026-125365?

CVE-2026-125365 is a high-severity vulnerability in harung1993 dollardollar, published on 9 Nov 2026. 

### Official description

DollarDollar through 4.4 contains a missing authorization vulnerability in add_expense() that allows authenticated users to modify other users' account balances by supplying foreign account_id values. Attackers can submit sequential account_id, destination_account_id, and group_id values to /add_expense to tamper with balances and inject expenses into foreign groups with an arbitrary payer.

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

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


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

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

## Is CVE-2026-125365 being exploited?

There is no known exploitation of CVE-2026-125365 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-125365 is a high-severity vulnerability in harung1993 dollardollar, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-125365 in the wild and no public exploit code.

Affected product: harung1993 dollardollar. 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-125365/ (Markdown: https://insights.sbomify.com/CVE-2026-125365/index.md)
```

## Sources

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

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