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
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
| Link | Providers |
|---|---|
| https://github.com/0xBS0D27/CVE-2025-56643 |
|
History
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:
Updated: 2025-11-18T17:42:16.393Z
Reserved: 2025-08-17T00:00:00.000Z
Link: CVE-2025-56643
No data.
Status : Received
Published: 2025-11-18T18:16:07.647
Modified: 2025-11-18T18:16:07.647
Link: CVE-2025-56643
No data.
OpenCVE Enrichment
No data.