# CVE-2026-94112: mayswind ezBookkeeping TOTP passcode replay in authentication

Source: https://junglewise.ai/threats/cve-2026-94112-mayswind-ezbookkeeping-before-2-0-0-fails-to-invalidate-totp  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-20. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-94112 · Severity: medium · CVSS 6.8 · Published 2026-09-20

mayswind ezBookkeeping is a personal bookkeeping application that supports two-factor authentication via TOTP codes. Before version 2.0.0, the application failed to invalidate TOTP codes after single use, allowing attackers who obtained user credentials and a captured authentication code to reuse that code repeatedly for about 90 seconds. This could enable account takeover without the legitimate user being aware their credentials were compromised.

Technologies: [Mayswind ezBookkeeping](https://junglewise.ai/threats/technologies/ezbookkeeping). Vendors: [Mayswind](https://junglewise.ai/threats/vendors/mayswind).

## Quick answers

**Is CVE-2026-94112 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-94112 being exploited in the wild.

**How severe is CVE-2026-94112?** Medium severity, with a CVSS score of 6.8, published 20 September 2026.

**Which products and versions are affected?** Mayswind ezBookkeeping before 2.0.0.

**Is there a fix for CVE-2026-94112?** A patch was published on 2026-09-16: v2.0.0 released with TOTP passcode invalidation fix Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-94112 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-94112?** Check whether you run Mayswind ezBookkeeping at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is a TOTP replay flaw in the two-factor authentication implementation. An attacker with valid credentials can capture a TOTP code and replay it during the acceptance window (approximately 90 seconds) for multiple authentication attempts, bypassing the intended security mechanism of single-use codes. The fix, released in version 2.0.0, implements proper passcode invalidation after a single use.

## Affected products

- mayswind ezBookkeeping before 2.0.0

## Timeline

- 2026-09-20: disclosed
- 2026-09-16: patched: v2.0.0 released with TOTP passcode invalidation fix

## References

- [https://github.com/mayswind/ezbookkeeping/commit/3dd6286d7a3ab0f980a6d36339b9c9c4df9467e4](https://github.com/mayswind/ezbookkeeping/commit/3dd6286d7a3ab0f980a6d36339b9c9c4df9467e4)
- [https://github.com/mayswind/ezbookkeeping/releases/tag/v2.0.0](https://github.com/mayswind/ezbookkeeping/releases/tag/v2.0.0)

## Related threats

- [ezBookkeeping IP spoofing via unsanitized X-Forwarded-For header](https://junglewise.ai/threats/cve-2026-86041-ezbookkeeping-is-an-open-source-self-hosted-personal-finance)
- [ezBookkeeping privilege escalation in token refresh](https://junglewise.ai/threats/cve-2026-105131-ezbookkeeping-1-2-0-before-2-0-1-contains-a-privilege-escalation)