{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-1897 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-1897 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-1897 is a medium-severity missing authorization vulnerability in WeKan, published on 5 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-1897 and fix it if it is affected.\n\nWhat it is: CVE-2026-1897 is a medium-severity missing authorization vulnerability in WeKan, published on 5 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-1897 in the wild and no public exploit code.\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-1897/ (Markdown: https://insights.sbomify.com/CVE-2026-1897/index.md)","id":"CVE-2026-1897","markdown":"https://insights.sbomify.com/CVE-2026-1897/index.md","name":"CVE-2026-1897","record":{"aliases":["GHSA-4xx4-65hp-28vf"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WeKan project management","requires_auth":"low_privilege","summary":"Remote attackers can access or modify position history data in WeKan due to missing authorization checks in the tracking module.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"wekan","vendor":"wekan_project"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-862","name":"Missing Authorization"}],"description":"A vulnerability was found in WeKan up to 8.20. Affected by this issue is some unknown functionality of the file server/methods/positionHistory.js of the component Position-History Tracking. The manipulation results in missing authorization. The attack may be performed from remote. Upgrading to version 8.21 can resolve this issue. The patch is identified as 55576ec17722db094835470b386162c9a662fb60. It is advisable to upgrade the affected component.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"WeKan Position-History Tracking positionHistory.js PositionHistoryBleed authorization","id":"CVE-2026-1897","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"WeKan LDAP User Sync syncUser.js SyncLDAPBleed access control","id":"CVE-2026-1898"},"packages":[],"prev":{"headline":"WeKan Migration Operation comprehensiveBoardMigration.js ComprehensiveBoardMigration MigrationBleed access control","id":"CVE-2026-1896"},"products":["WeKan"],"published":"2026-02-05","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-23","vendors":["n/a"]},"summary":"Remote attackers can access or modify position history data in WeKan due to missing authorization checks in the tracking module.","url":"https://insights.sbomify.com/CVE-2026-1897/"}