Vulnerability · Published Oct 4, 2026 · Assigned by VulnCheck

CVE-2026-105131mayswind ezBookkeeping 1.2.0 before 2.0.1 Privilege Escalation via Token Refresh Endpoint

Medium 5.4

In plain English

A medium-severity incorrect authorization in ezBookkeeping from mayswind. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 10% of all known vulnerabilities).

Severity (CVSS 3.1)5.4Medium

Exploit odds (30 days)0.2%top 90.4% of all CVEs

Exploited in the wildNo reportsCISA SSVC: none

Attack toolingNoneno public tooling known

Official 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.

Affected products (as reported)

Vendor	Product	Versions
mayswind	ezBookkeeping	1.2.0 – before 2.0.1

Weakness: CWE-863 · Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

References

GitHub Security Advisory (GHSA-wq25-mpcf-2mfc) vendor-advisory
Patch Commit patch
ezBookkeeping v2.0.1 Release Notes release-notes
TokenRefreshHandler at v2.0.0 technical-description
https://github.com/mayswind/ezbookkeeping product
VulnCheck Advisory: mayswind ezBookkeeping 1.2.0 before 2.0.1 Privilege Escalation via Token Refresh Endpoint third-party-advisory