{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-52892 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-52892 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-52892 is a medium-severity missing authorization vulnerability in wekan, published on 15 Jul 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-52892 and fix it if it is affected.\n\nWhat it is: CVE-2026-52892 is a medium-severity missing authorization vulnerability in wekan, published on 15 Jul 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-52892 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-52892/ (Markdown: https://insights.sbomify.com/CVE-2026-52892/index.md)","id":"CVE-2026-52892","markdown":"https://insights.sbomify.com/CVE-2026-52892/index.md","name":"CVE-2026-52892","record":{"aliases":["GHSA-6733-4wgq-8xvr"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Wekan kanban board","requires_auth":"low_privilege","summary":"Read-only users can create, modify, or delete custom fields in Wekan due to missing write-level authorization checks on API endpoints.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Wekan is open source kanban built with Meteor. Prior to 9.32, Wekan REST handlers in server/models/customFields.js use read-level Authentication.checkBoardAccess instead of write-level Authentication.checkBoardWriteAccess for mutating custom-field routes. A read-only board member can call POST, PUT, and DELETE handlers for /api/boards/:boardId/custom-fields and custom-field dropdown items to create, update, or delete board custom fields. This issue is fixed in version 9.32.","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":"Missing authorization in wekan","id":"CVE-2026-52892","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Wekan: OIDC Account Takeover via Unconditional Email-Based Account Merge in onCreateUser hook","id":"CVE-2026-52893"},"packages":[],"prev":{"headline":"Wekan: Shell Injection via Avatar Upload","id":"CVE-2026-52891"},"products":["wekan"],"published":"2026-07-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-07-16","vendors":["wekan"]},"summary":"Read-only users can create, modify, or delete custom fields in Wekan due to missing write-level authorization checks on API endpoints.","url":"https://insights.sbomify.com/CVE-2026-52892/"}