VulnerabilityPublished 18 Nov 2025Updated 19 Nov 2025

CVE-2025-56643: wiki.js · Insufficient Session Expiration

Affects wiki.jsSource CVE Database V5

Not known to be exploited · CVSS 9.1 Critical.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

9.1Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubrequarks/wiki.js`pkg:github/requarks/wiki.js`Other threats	Affected =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

To mitigate CVE-2025-56643, organizations should prioritize upgrading Wiki.js to a version where the vulnerability is patched once available. In the interim, administrators can implement the following specific measures: 1) Introduce server-side token revocation lists or blacklists to invalidate JWTs upon logout or manual session termination. 2) Reduce JWT token lifetime to minimize the window of exposure if tokens are compromised. 3) Implement additional session management controls such as rotating tokens on sensitive operations and enforcing multi-factor authentication (MFA) to reduce the risk of token theft exploitation. 4) Monitor authentication logs and GraphQL API usage for anomalous token reuse patterns indicative of session hijacking. 5) Restrict access to the Wiki.js instance via network segmentation and VPNs to limit exposure. 6) Educate users on secure logout practices and the risks of token reuse. 7) Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block suspicious JWT usage. These steps go beyond generic advice by focusing on compensating controls that address the core issue of token invalidation and session integrity.

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.

Impact

For European organizations, the impact of CVE-2025-56643 can be severe. Unauthorized reuse of JWT tokens can lead to unauthorized access to sensitive corporate knowledge bases, intellectual property, or internal documentation. This could facilitate data breaches, insider threat activities, or lateral movement within networks. Organizations in regulated sectors such as finance, healthcare, and government are particularly vulnerable due to strict data protection requirements under GDPR and other regulations. The persistence of valid tokens after logout undermines trust in session management and can lead to compliance violations if unauthorized access results in data leakage. Additionally, Wiki.js is often used as a collaborative platform, so compromised accounts could allow attackers to alter or delete critical documentation, impacting operational integrity. The lack of availability impact means systems remain operational, potentially masking the presence of an ongoing breach. European entities with remote or hybrid workforces relying on web-based collaboration tools are at increased risk due to the network-exploitable nature of the vulnerability.

CWE-613Insufficient Session Expiration (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization."
Implementation
Set sessions/credentials expiration date.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.1 (opens in a new tab)
V2.8.6 (opens in a new tab)
V3.6.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/0xBS0D27/CVE-2025-56643 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Nov 2025, 19:10 UTC

WeaknessesCWE-613

Technical details

References

Community reviews

Related threats