CVE-2026-105131 Details
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.
A privilege escalation vulnerability has been identified in ezBookkeeping versions 1.2.0 prior to 2.0.1. This vulnerability allows attackers with an API token to obtain a full session token by exploiting the '/api/v1/tokens/refresh.json' endpoint. The issue arises because the TokenRefreshHandler does not validate the type of token being refreshed. As a result, attackers can trade short-lived or IP-restricted API tokens for 30-day normal session tokens, bypassing API token expiration and allowlists. The vulnerability is compounded by an API token created to never expire, which is erroneously issued with a validity extending to the year 2319, due to an integer overflow.
Users can update to ezBookkeeping version 2.0.1, where this vulnerability has been patched.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Oct 4, 2026CISA-ADP
Assessed Oct 5, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-863 | Incorrect Authorization | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| mayswind ezBookkeeping | >= 1.2.0, < 2.0.1 (semver) |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 5, 2026 | CVE Modified | CISA-ADP |
| Oct 4, 2026 | New CVE Received | [email protected] |
Volerion