Lack of JWT Expiration after Log Out 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-26180 | Payload does not invalidate JWTs after log out |
Github GHSA |
GHSA-5v66-m237-hwf7 | Payload does not invalidate JWTs after log out |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.415% 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 | Payload uses JSON Web Tokens (JWT) for authentication. After log out JWT is not invalidated, which allows an attacker who has stolen or intercepted token to freely reuse it until expiration date (which is by default set to 2 hours, but can be changed). This issue has been fixed in version 3.44.0 of Payload. | |
| Title | Lack of JWT Expiration after Log Out in PayloadCMS | |
| Weaknesses | CWE-613 | |
| References |
| |
| Metrics |
cvssV4_0
|