CVE-2026-122324 · Package
NO FIX YET
SplitPro through 2.1.6 lets any logged-in user fetch expense details for expenses they do not belong to by supplying an arbitrary expenseId. An attacker who has an expense UUID, such as a former group participant, can read expense notes, recurrence schedules, and full user records of participants and group members.
first public Nov 5, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams that self-host SplitPro 2.1.6 or earlier and have user accounts on the instance are exposed, since the flaw is an authorization check missing on expense.getExpenseDetails. Instances where only the operator uses the app, or that are kept off the internet, carry less risk. The sources do not say whether the fixed version is named in the product data.
Not affected if no-external-accounts, single-user-instance
Who cares self-hosted, splitpro
Unknown from the sources.
No fix yet, per the sources.
SplitPro through 2.1.6 contains an authorization bypass vulnerability that allows authenticated users to read other users' expenses by supplying arbitrary expenseId values to expense.getExpenseDetails. Attackers who obtain an expense UUID, such as removed former participants, can retrieve expense notes, recurrence schedules, and full user rows of participants and group members.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.