{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-56643 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-56643 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-56643 is a critical vulnerability in n/a, published on 18 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-56643 and fix it if it is affected.\n\nWhat it is: CVE-2025-56643 is a critical vulnerability in n/a, published on 18 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-56643 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-56643/ (Markdown: https://insights.sbomify.com/CVE-2025-56643/index.md)","id":"CVE-2025-56643","markdown":"https://insights.sbomify.com/CVE-2025-56643/index.md","name":"CVE-2025-56643","record":{"aliases":["GHSA-523q-32qm-5jpf"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["security_bypass","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Wiki.js","requires_auth":"none","summary":"Wiki.js fails to invalidate JWT tokens upon logout, allowing attackers with stolen tokens to maintain unauthorized access to the system.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wiki.js","vendor":"requarks"}],"cvss":{"score":9.1,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-11-06","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-11-06T18:48:07Z","kind":"github_poc","ref":"https://github.com/0xBS0D27/CVE-2025-56643","stars":1,"title":"Public reference for CVE-2025-56643 – Wiki.js 2.5.307 JWT Session Vulnerability"}],"tier":"poc_unverified"},"has_fix":false,"headline":"Security feature bypass in n/a","id":"CVE-2025-56643","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"@farmfe/core is Missing Origin Validation in WebSocket","id":"CVE-2025-56647"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2025-56630"},"products":["n/a"],"published":"2025-11-18","related":[{"cvss_score":8.6,"headline":"Wiki.js: Privilege Escalation via Missing Group Validation in users.update","id":"CVE-2026-44224","kev_date_added":null,"published":"2026-05-12"},{"cvss_score":8.6,"headline":"Directory Traversal in Wiki.js","id":"CVE-2020-15236","kev_date_added":null,"published":"2020-10-05"},{"cvss_score":8.2,"headline":"Stored XSS via SVG in Requarks/wiki","id":"CVE-2021-43855","kev_date_added":null,"published":"2021-12-27"},{"cvss_score":8.2,"headline":"Stored XSS in non-image uploads in Requarks/wiki","id":"CVE-2021-43856","kev_date_added":null,"published":"2021-12-27"},{"cvss_score":8.1,"headline":"Improper write access check in Requarks/wiki","id":"CVE-2022-23654","kev_date_added":null,"published":"2022-02-22"},{"cvss_score":7.6,"headline":"XSS in Wiki.js","id":"CVE-2021-21383","kev_date_added":null,"published":"2021-03-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-11-19","vendors":["n/a"]},"summary":"Wiki.js fails to invalidate JWT tokens upon logout, allowing attackers with stolen tokens to maintain unauthorized access to the system.","url":"https://insights.sbomify.com/CVE-2025-56643/"}