{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2207 exists.","fix":"No fix has been published for CVE-2026-2207 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-2207 is a medium-severity vulnerability in WeKan, published on 8 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-2207 and fix it if it is affected.\n\nWhat it is: CVE-2026-2207 is a medium-severity vulnerability in WeKan, published on 8 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2207 exists.\n\nAffected product: WeKan. 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-2026-2207/ (Markdown: https://insights.sbomify.com/CVE-2026-2207/index.md)","id":"CVE-2026-2207","markdown":"https://insights.sbomify.com/CVE-2026-2207/index.md","name":"CVE-2026-2207","record":{"aliases":["GHSA-p69q-x7rq-85qp"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WeKan web application","requires_auth":"none","summary":"Remote attackers can exploit an information disclosure vulnerability in WeKan's activity publication handler to access sensitive data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"wekan","vendor":"wekan_project"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X","version":"4.0"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"A weakness has been identified in WeKan up to 8.20. This issue affects some unknown processing of the file server/publications/activities.js of the component Activity Publication Handler. Executing a manipulation can lead to information disclosure. It is possible to launch the attack remotely. Upgrading to version 8.21 is capable of addressing this issue. This patch is called 91a936e07d2976d4246dfe834281c3aaa87f9503. You should upgrade the affected component.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"WeKan Activity Publication activities.js LinkedBoardActivitiesBleed information disclosure","id":"CVE-2026-2207","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"WeKan Rules rules.js RulesBleed authorization","id":"CVE-2026-2208"},"packages":[],"prev":{"headline":"WeKan Administrative Repair fixDuplicateLists.js FixDuplicateBleed access control","id":"CVE-2026-2206"},"products":["WeKan"],"published":"2026-02-08","related":[{"cvss_score":9.3,"headline":"Wekan has Cross-Board IDOR in Custom Fields Update Endpoints","id":"CVE-2026-30843","kev_date_added":null,"published":"2026-03-06"},{"cvss_score":9.3,"headline":"Wekan Vulnerable to SSRF through Lack of Validation or Filtering in Attachment URL Loading","id":"CVE-2026-30844","kev_date_added":null,"published":"2026-03-06"},{"cvss_score":9.3,"headline":"Wekan Credential Leak via notificationUsers Publication Exposes Password Hashes and Session Tokens","id":"CVE-2026-30847","kev_date_added":null,"published":"2026-03-06"},{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2025-65780","kev_date_added":null,"published":"2025-12-15"},{"cvss_score":8.7,"headline":"Wekan Exposes All Global Webhook Integrations through globalwebhooks Publication","id":"CVE-2026-30846","kev_date_added":null,"published":"2026-03-06"},{"cvss_score":8.7,"headline":"WeKan \u003c 8.19 LDAP Authentication Filter Injection","id":"CVE-2026-25560","kev_date_added":null,"published":"2026-02-07"},{"cvss_score":8.2,"headline":"Denial of service in n/a","id":"CVE-2025-65781","kev_date_added":null,"published":"2025-12-15"}],"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)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-23","vendors":["n/a"]},"summary":"Remote attackers can exploit an information disclosure vulnerability in WeKan's activity publication handler to access sensitive data.","url":"https://insights.sbomify.com/CVE-2026-2207/"}