Requarks Wiki.js 2.5.307 does not properly revoke or invalidate active JWT tokens when a user logs out. As a result, previously issued tokens remain valid and can be reused to access the system, even after logout. This behavior affects session integrity and may allow unauthorized access if a token is compromised. The issue is present in the authentication resolver logic and affects both the GraphQL endpoint and the logout mechanism.
Metrics
Affected Vendors & Products
References
| Link | Providers |
|---|---|
| https://github.com/0xBS0D27/CVE-2025-56643 |
|
History
Fri, 21 Nov 2025 09:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Requarks
Requarks wiki.js |
|
| Vendors & Products |
Requarks
Requarks wiki.js |
Wed, 19 Nov 2025 17:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-613 | |
| Metrics |
cvssV3_1
|
Tue, 18 Nov 2025 18:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Requarks Wiki.js 2.5.307 does not properly revoke or invalidate active JWT tokens when a user logs out. As a result, previously issued tokens remain valid and can be reused to access the system, even after logout. This behavior affects session integrity and may allow unauthorized access if a token is compromised. The issue is present in the authentication resolver logic and affects both the GraphQL endpoint and the logout mechanism. | |
| References |
|
Status: PUBLISHED
Assigner: mitre
Published: 2025-11-18T00:00:00.000Z
Updated: 2025-11-19T16:50:05.856Z
Reserved: 2025-08-17T00:00:00.000Z
Link: CVE-2025-56643
Updated: 2025-11-19T16:25:42.911Z
Status : Awaiting Analysis
Published: 2025-11-18T18:16:07.647
Modified: 2025-11-19T19:14:59.327
Link: CVE-2025-56643
No data.
ReportizFlow