Skip to main content
VulnerabilityPublished

CVE-2025-56643: Requarks Wiki.js 2.5.307 does not properly revoke or invalidate active JWT tokens when a user logs out

Source GCVE Database

0
Compare
Authoritative record:CVE-2025-56643· Critical 9.1

Not known to be exploited · CVSS 9.1 Critical.

Data as of 13 Nov 2026, 20:36 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.19.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubrequarks/wiki.jspkg:github/requarks/wiki.jsOther threatsAffected
  • =2.5.307
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, consider implementing additional controls such as short token lifetimes or manual token revocation mechanisms if supported.

Description

Requarks Wiki.js version 2.5.307 has a vulnerability where JWT tokens are not properly revoked or invalidated upon user logout. This flaw allows previously issued tokens to remain valid and potentially be reused to access the system after logout, compromising session integrity and enabling unauthorized access if tokens are compromised.

References

Community reviews

Loading reviews…