CVE-2026-105131CWE-863broken-access-control

CVE-2026-105131

Medium · published October 4, 2026

CVSS v3.1
5.4
EPSS
0%
Percentile
9.1
In the wild
Unconfirmed
What it is

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.

The record
Technical detail
CVSS v3.1
5.4 · MEDIUM
Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
CVSS v4.0
5.3 · 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
EPSS
0.00198 · 9.1th percentile
Weakness
CWE-863 · Incorrect Authorization
Published
2026-10-04T06:16Z
References (6)
https://github.com/mayswind/ezbookkeeping · [email protected]https://github.com/mayswind/ezbookkeeping/blob/v2.0.0/pkg/api/tokens.go#L327-L380 · [email protected]https://github.com/mayswind/ezbookkeeping/commit/9a92b07be8a7034665abfdb35b036210a1d57bf9 · [email protected]https://github.com/mayswind/ezbookkeeping/releases/tag/v2.0.1 · [email protected]https://github.com/mayswind/ezbookkeeping/security/advisories/GHSA-wq25-mpcf-2mfc · [email protected]https://www.vulncheck.com/advisories/mayswind-ezbookkeeping-1.2.0-before-2.0.1-privilege-escalation-via-token-refresh-endpoint · [email protected]
EPSS history
Timeline
  • 07 OCT 03:39Z
    EPSS moved — → 0%
    epss
  • 04 OCT 01:20Z
    mayswind ezBookkeeping 1.2.0 before 2.0.1 Privilege Escalation via Token Refresh Endpoint
    cvelistv5