CVE-2026-105131
MediumCVSS 5.4Exploitation Probability (EPSS)
Low risk9th percentile - higher than 9% of all known CVEs
Summary
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.
Risk Assessment
An attacker with an API token can obtain a long-lived session token that bypasses restrictions, leading to unauthorized account and data access.
Recommendation
Update ezBookkeeping to version 2.0.1 or later, which verifies token type in TokenRefreshHandler.
Other vulnerabilities in ezBookkeeping
Original NVD description (English source)
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.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS

