User Session Fixation after Account Removal in PayloadCMS
Payload CMS Payload
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| payload npm |
|
|
| @payloadcms/next npm |
|
|
| @payloadcms/graphql npm |
Payload CMS Payload
| Product | Affected | Fixed in |
|---|---|---|
| payload npm |
|
|
| @payloadcms/next npm |
|
|
| @payloadcms/graphql npm |
< 3.44.0
|
A Session Fixation vulnerability existed in Payload's SQLite adapter due to identifier reuse during account creation. A malicious attacker could create a new account, save its JSON Web Token (JWT), and then delete the account, which did not invalidate the JWT. As a result, the next newly created user would receive the same identifier, allowing the attacker to reuse the JWT to authenticate and perform actions as that user.
This issue has been fixed in version 3.44.0 of Payload.
From the CVE record · CERT-PL
Payload's SQLite adapter reused account identifiers after deletion and did not invalidate the deleted account's JWT. An attacker who could create and delete an account could retain its JWT and use it to authenticate as the next user assigned that identifier. No victim interaction is described.
Check Payload installations using the SQLite adapter with payload, @payloadcms/next, or @payloadcms/graphql versions earlier than 3.44.0.