Skip to main content
VulnerabilityPublished Updated

CVE-2026-94112: mayswind ezBookkeeping · Authentication Bypass by Capture-replay

Affects mayswind ezBookkeepingSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.6 High : upgrade to 2.0.0 soon.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 4.0 base score
7.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.0.0
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Sep 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 5 Nov 2026.

What to do

Upgrade mayswind ezBookkeeping to 2.0.0.

Affected software

ProductAffectedFixed in
mayswindezBookkeepingAffected
  • <2.0.0
Fixed in
  • 2.0.0
GitHubezBookkeepingpkg:github/ezBookkeepingOther threatsAffected
  • <2.0.0
Fixed in
  • 2.0.0

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

AI-suggested

A fix is available in version 2.0.0 of mayswind ezBookkeeping. Users should upgrade to version 2.0.0 or later to ensure TOTP passcodes are properly invalidated after use, preventing replay attacks. Until upgrading, users should be aware of the risk of passcode replay within the acceptance window and consider additional compensating controls if possible.

Description

mayswind ezBookkeeping versions before 2.0.0 have a vulnerability where TOTP passcodes are not invalidated after use. This allows attackers who have captured a valid passcode to replay it within the acceptance window of approximately 90 seconds, enabling multiple unauthorized authentications without detection.

References

Community reviews

Loading reviews…