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.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Attack Requirements
None
No additional conditions
Privileges Required
Low
Basic privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
Low
Partial data leak
Integrity
Low
Partial data modification
Availability
None
No disruption
CVSS Vector v4.0
Weakness Type (CWE)
Vulnerable Products 1
| Configuration | From (including) | Up to (excluding) |
|---|---|---|
|
Mayswind Ezbookkeeping
cpe:2.3:a:mayswind:ezbookkeeping:*:*:*:*:*:*:*:*
|
1.2.0
|
2.0.1
|
References 6
https://github.com/mayswind/ezbookkeeping
disclosure@vulncheck.com
https://github.com/mayswind/ezbookkeeping/blob/v2.0.0/pkg/api/tokens.go#L327-L3…
disclosure@vulncheck.com
https://github.com/mayswind/ezbookkeeping/commit/9a92b07be8a7034665abfdb35b0362…
disclosure@vulncheck.com
https://github.com/mayswind/ezbookkeeping/releases/tag/v2.0.1
disclosure@vulncheck.com
https://github.com/mayswind/ezbookkeeping/security/advisories/GHSA-wq25-mpcf-2m…
disclosure@vulncheck.com
https://www.vulncheck.com/advisories/mayswind-ezbookkeeping-1.2.0-before-2.0.1-…
disclosure@vulncheck.com