# CVE-2026-94112: mayswind ezBookkeeping before 2.0.0 TOTP Replay Attack

> Attackers can replay captured TOTP codes to bypass two-factor authentication and take over accounts in ezBookkeeping.

- **Severity:** High 7.6 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-j95g-6g2h-3f33, GHSA-p6qr-48g6-97q3

## What is CVE-2026-94112?

CVE-2026-94112 is a high-severity authentication bypass vulnerability in mayswind ezBookkeeping, published on 20 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

mayswind ezBookkeeping before 2.0.0 fails to invalidate TOTP passcodes after use, allowing attackers to replay captured codes within the acceptance window. Attackers with stolen credentials can authenticate and reuse a captured passcode against multiple authorization attempts for approximately 90 seconds without detection.

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

## Which versions are affected by CVE-2026-94112?


## How do I fix CVE-2026-94112?

No fix has been published for CVE-2026-94112 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-94112 being exploited?

There is no known exploitation of CVE-2026-94112 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-94112 and fix it if it is affected.

What it is: CVE-2026-94112 is a high-severity authentication bypass vulnerability in mayswind ezBookkeeping, published on 20 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-94112 in the wild and no public exploit code.

Affected product: mayswind ezBookkeeping. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-94112/ (Markdown: https://insights.sbomify.com/CVE-2026-94112/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-94112
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-94112
- OSV: https://osv.dev/vulnerability/CVE-2026-94112

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-94112/
Summaries are generated and may contain mistakes; the official description above is the record.