Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Requarks | Wiki.js | — |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.382% probability within 30 days)
| Link | Providers |
|---|---|
| https://github.com/0xBS0D27/CVE-2025-56643 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:requarks:wiki.js:2.5.307:*:*:*:*:*:*:* |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Requarks
Requarks wiki.js |
|
| Vendors & Products |
Requarks
Requarks wiki.js |
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-613 | |
| Metrics |
cvssV3_1
|
| 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 |
|