Skip to main content
VulnerabilityPublished Updated

CVE-2026-105131: mayswind ezBookkeeping · Incorrect Authorization

Affects mayswind ezBookkeepingSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.0.1 when convenient.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.0.1
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade mayswind ezBookkeeping to 2.0.1.

Affected software

ProductAffectedFixed in
mayswindezBookkeepingAffected
  • >=1.2.0 <2.0.1
Fixed in
  • 2.0.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

ezBookkeeping versions 1.2.0 up to but not including 2.0.1 contain a privilege escalation vulnerability. Attackers with an API token can exploit the token refresh endpoint to obtain a full session token without proper authorization checks. This allows bypassing API token expiry and allowlists, potentially extending access privileges for 30 days.

References

Community reviews

Loading reviews…