CVE-2022-39263 affects applications using the next-auth Email Provider and @next-auth/upstash-redis-adapter before version 3.0.2. The vulnerability stems from insufficient token verification in the email callback flow, where only the identifier (email) was checked, not the token. This allows an attacker who knows a victim's email and the token's expiration duration to bypass authentication. Rated 8.1 HIGH (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), this vulnerability has a network attack vector and high impact on confidentiality, integrity, and availability, but requires high attack complexity due to needing knowledge of the token's expiration. There is no evidence of active exploitation, nor are there public exploits available in Metasploit, Nuclei, or ExploitDB. Community discussion and media coverage are minimal, indicating low public awareness.
| Vendor | Product | Version(s) | CPE |
|---|---|---|---|
< 3.0.2CPE matchmatch criteria | cpe:2.3:a:nextauth.js:next-auth:*:*:*:*:*:node.js:*:* |
CVSS version used by this source: 3.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
The average CVE in this peer group has 0.0 Twitter, 0.1 Reddit, 0.1 Bluesky, 0.0 Mastodon, and 0.2 GitHub mentions.
No media coverage found for this CVE.
The average CVE in this peer group has 0.1 InfoSec Media, 0.0 Vendor Blog, and 0.0 Security Researcher mentions.