Account access after logout via reusable JWT
Published Aug 29, 2025 · Updated Aug 29, 2025
Insufficient session expiration in Payload before 3.44.0 allows remote attackers with a stolen JWT to retain account access after logout. The logout path deletes the client cookie but leaves the stateless signed token valid, so authentication continues to accept it until tokenExpiration, two hours by default. Exploitation requires possession of a valid token and grants only the permissions of the affected account.
Summary
What happened
Insufficient session expiration in Payload before 3.44.0 allows remote attackers with a stolen JWT to retain account access after logout. The logout path deletes the client cookie but leaves the stateless signed token valid, so authentication continues to accept it until tokenExpiration, two hours by default. Exploitation requires possession of a valid token and grants only the permissions of the affected account.
The record
- CVE
- CVE-2025-4643
- Published
- Aug 29, 2025
- Updated
- Aug 29, 2025
- Vendor
- Payload CMS
- Product
- Payload
- Classifications
- CWE-613, CAPEC-115, T1078
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 29, 2025CVE publishedPublication date reported by the CVE source.
- Aug 29, 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=0 <3.44.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
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