Description
ezBookkeeping 1.2.0 before 2.0.1 contains a privilege escalation vulnerability that allows attackers holding an API token to obtain a full session token via /api/v1/tokens/refresh.json. Because TokenRefreshHandler never checks token type, attackers can exchange short-lived or IP-restricted API tokens for 30-day normal session tokens that bypass API token expiry and allowlists.
References6
- github.com/mayswind/ezbookkeeping
- github.com/mayswind/ezbookkeeping/blob/v2.0.0/pkg/api/tokens.go…
- github.com/mayswind/ezbookkeeping/commit/9a92b07be8a7034665abfd…
- github.com/mayswind/ezbookkeeping/releases/tag/v2.0.1
- github.com/mayswind/ezbookkeeping/security/advisories/GHSA-wq25…
- www.vulncheck.com/advisories/mayswind-ezbookkeeping-1.2.0-befor…
Metrics
- CVSS 3.1
-
5.4
MEDIUM
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N - CVSS 4.0
-
5.3
MEDIUM
Score source: CNA
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/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 - EPSS — exploit probability
- 0% percentile: 10 · as of 10 November 2026
- CWE
- CWE-863
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.