2FAuth: Missing Authorization on Share Recipients Endpoint Allows Cross-User Account Enumeration
- Exploited
- No known exploitation
- Fix
- Fixed in 8.0.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 8.0.0.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 10/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
2FAuth, a web app for managing two-factor authentication accounts, is missing an authorization check on its share recipients endpoint. A remote attacker with a low-privilege authenticated account can, when account sharing is enabled, use that endpoint on accounts owned by other users to enumerate registered user IDs and display names, test exact email addresses, and view those accounts' sharing relationships.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
2FAuth is a web app to manage Two-Factor Authentication (2FA) accounts and generate their security codes. Prior to 8.0.0, the recipients() method in app/Api/v1/Controllers/TwoFAccountShareController.php receives a caller-selected TwoFAccount through Laravel model binding but does not call the manageShares authorization policy before listing its recipients. When account sharing is enabled, an authenticated user can call GET /api/v1/twofaccounts/{victimId}/recipients for accounts owned by other users, enumerate registered user IDs and display names, test exact email addresses with filter[nameOrEmail], and inspect each account's sharing relationships. This issue is fixed in version 8.0.0.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.5/10CVSS 6.5
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 8.0.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Bubka 2FAuth
fixed in 8.0.0
Evidence 3
- Advisory
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-63437
Is CVE-2026-63437 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-63437?
2FAuth: before 8.0.0.Source: cve.now feed data
How do I fix CVE-2026-63437?
Upgrade to a fixed version: 8.0.0.Source: cve.now feed data