Account takeover via identifier-only token lookup
Published Sep 28, 2022 · Updated Apr 23, 2025
Improper authentication in the NextAuth.js Upstash Redis Adapter before 3.0.2 allows remote attackers to sign in as another user. The createVerificationToken and useVerificationToken methods key Redis records only by email identifier, so a callback token is not matched to the stored token. The target must use both the Email Provider and affected adapter; exploitation requires the victim's email address and user interaction, and success grants access to the victim's account.
Summary
What happened
Improper authentication in the NextAuth.js Upstash Redis Adapter before 3.0.2 allows remote attackers to sign in as another user. The createVerificationToken and useVerificationToken methods key Redis records only by email identifier, so a callback token is not matched to the stored token. The target must use both the Email Provider and affected adapter; exploitation requires the victim's email address and user interaction, and success grants access to the victim's account.
The record
- CVE
- CVE-2022-39263
- Published
- Sep 28, 2022
- Updated
- Apr 23, 2025
- Vendor
- Auth.js
- Product
- NextAuth.js
- Classifications
- CWE-285, T1078
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 28, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record 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=< 3.0.2
What conditions does exploitation require?
What is affected?
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.
Public exploit references
No public exploit references are available in this record.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo