User Session Fixation after Account Removal in PayloadCMS
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Payload CMS | Payload | unaffected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Payloadcms | Payload | — |
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-26181 | Payload's SQLite adapter Session Fixation vulnerability |
Github GHSA |
GHSA-26rv-h2hf-3fw4 | Payload's SQLite adapter Session Fixation vulnerability |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.426% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Payloadcms
Payloadcms payload |
|
| Vendors & Products |
Payloadcms
Payloadcms payload |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | User Session Fixation after Account Removal in PayloadCMS | |
| Weaknesses | CWE-384 | |
| References |
| |
| Metrics |
cvssV4_0
|