Authentication bypass via reusable TOTP passcodes
Published Sep 20, 2026 · Updated Sep 20, 2026
Authentication bypass in Mayswind ezBookkeeping before 2.0.0 allows remote attackers to open a second session with a captured TOTP code. The authorization handlers validate a submitted code against its time window but do not record it as consumed after successful use. Exploitation requires stolen account credentials and a captured valid code; a successful replay creates an independent session that remains valid after the code expires.
Summary
What happened
Authentication bypass in Mayswind ezBookkeeping before 2.0.0 allows remote attackers to open a second session with a captured TOTP code. The authorization handlers validate a submitted code against its time window but do not record it as consumed after successful use. Exploitation requires stolen account credentials and a captured valid code; a successful replay creates an independent session that remains valid after the code expires.
The record
- CVE
- CVE-2026-94112
- Published
- Sep 20, 2026
- Updated
- Sep 20, 2026
- Vendor
- Mayswind
- Product
- ezBookkeeping
- Classifications
- CWE-294, T1078.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 20, 2026CVE publishedPublication date reported by the CVE source.
- Sep 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.0.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- GHSA-p6qr-48g6-97q3 replay reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started