CVE-2025-4643: Lack of JWT Expiration after Log Out in PayloadCMS

Published Aug 29, 2025
·
Updated

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.

Affected Software

4 affected componentsFixes available
Payload Payload<3.44.0
npm/@payloadcms/graphql<3.44.0
3.44.0
npm/@payloadcms/next<3.44.0
3.44.0
npm/payload<3.44.0
3.44.0

Event History

Aug 29, 2025
CVE Published
via MITRE·10:01 AM
Data Sourced
via MITRE·10:01 AM
DescriptionWeakness
Data Sourced
via NVD·10:15 AM
DescriptionSeverityWeakness
Advisory Published
via GitHub·12:31 PM
Data Sourced
via GitHub·12:31 PM
DescriptionWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-4643?

CVE-2025-4643 has a Medium severity rating due to the potential for token reuse after logout.

2

How do I fix CVE-2025-4643?

To fix CVE-2025-4643, implement token invalidation upon user logout in your authentication workflow.

3

Which versions of Payload are affected by CVE-2025-4643?

CVE-2025-4643 affects Payload versions prior to 3.44.0.

4

What is the impact of CVE-2025-4643?

The impact of CVE-2025-4643 allows attackers to reuse JSON Web Tokens after logout until their expiration.

5

How can I mitigate the risks of CVE-2025-4643?

Mitigating the risks of CVE-2025-4643 involves ensuring that JWTs are invalidated immediately upon user logout.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203