DollarDollar through 4.4 Missing Authorization in /add_expense Balance Tampering
Affects DollarDollar through 4.4 on multi-user instances, where any authenticated user can change other users' balances. No fixed release is listed.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- 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. Affects DollarDollar through version 4.4 (<= 4.4). Confirmed on commit afe9e32f83e92ff08089cc6b74280b83cd2d7ed0 on main; no tagged releases exist. Applies to a multi-user instance where other accounts exist on the same instance.
- Last modified
- 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? →
- 20/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
Summary
DollarDollar through the affected release is vulnerable to a missing authorization flaw in its expense-adding function, which lets a logged-in user change other users' account balances and add expenses to other users' groups. An attacker can do this remotely over the network with only a low-privilege login and no action from the victim.
Read the original 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch5/5No patch listed yet
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 27 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affects DollarDollar through version 4.4 (<= 4.4). Confirmed on commit afe9e32f83e92ff08089cc6b74280b83cd2d7ed0 on main; no tagged releases exist. Applies to a multi-user instance where other accounts exist on the same instance.Workaround: The checked facts give no workaround. The described exposure depends on other accounts existing on the same instance, so that is the setup the advisory points to.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- harung1993 dollardollar
through 4.4
Evidence 4
- Report
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125365
Is CVE-2026-125365 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 supply foreign account_id values to the /add_expense endpoint. This modifies other users' account balances and injects expenses into other users' groups with an arbitrary payer.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-125365?
dollardollar: through 4.4.Source: cve.now feed data
Am I affected, and how do I check?
The issue is listed for DollarDollar through version 4.4, confirmed on commit afe9e32f83e92ff08089cc6b74280b83cd2d7ed0 on main, since no tagged releases exist. It applies to multi-user instances where other accounts exist on the same instance.Source: vulncheck.com, github.com
How do I fix CVE-2026-125365?
The sources give no fixed version or upgrade target. There is no upgrade to apply based on the checked facts.Source: vulncheck.com, github.com
What if there's no patch?
The checked facts give no workaround. The described exposure depends on other accounts existing on the same instance, so that is the setup the advisory points to.Source: vulncheck.com, github.com