{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68899 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-68899 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-68899 is a high-severity cross-site scripting vulnerability in wekan, published on 19 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-68899 and fix it if it is affected.\n\nWhat it is: CVE-2026-68899 is a high-severity cross-site scripting vulnerability in wekan, published on 19 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-68899 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-68899/ (Markdown: https://insights.sbomify.com/CVE-2026-68899/index.md)","id":"CVE-2026-68899","markdown":"https://insights.sbomify.com/CVE-2026-68899/index.md","name":"CVE-2026-68899","record":{"aliases":["GHSA-jhph-whx8-wq6p"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Wekan kanban board","requires_auth":"low_privilege","summary":"Authenticated users can bypass MIME validation to store malicious HTML, leading to stored XSS and potential account takeover in Wekan deployments lacking the file binary.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"Wekan is open source kanban built with Meteor. Prior to 9.90, isFileValid() in models/fileValidation.js used the Unix file command for content-based MIME detection, but detectMimeFromFile() silently returned undefined when that binary was unavailable and the validation fell back to the attacker-controlled fileObj.type supplied through server/routes/attachmentApi.js. On deployments with WITH_API=true and no file binary, an authenticated board member could label HTML containing JavaScript as image/png, bypass the dangerous MIME check, and store active content under the Wekan origin for execution when another user opened it. Version 9.90 adds looksLikeDangerousMarkup() to inspect file bytes and force dangerous-content scanning when MIME detection is unavailable. This issue is fixed in version 9.90.","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: File Upload MIME Type Validation Bypass — Stored XSS via Missing System Binary Fallback","id":"CVE-2026-68899","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Wekan: Stored XSS in HTML board exports through a card-title second parse","id":"CVE-2026-68900"},"packages":[],"prev":{"headline":"Windows iSCSI Denial of Service Vulnerability","id":"CVE-2026-68898"},"products":["wekan"],"published":"2026-08-19","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":"total"},"state":"PUBLISHED","updated":"2026-08-21","vendors":["wekan"]},"summary":"Authenticated users can bypass MIME validation to store malicious HTML, leading to stored XSS and potential account takeover in Wekan deployments lacking the file binary.","url":"https://insights.sbomify.com/CVE-2026-68899/"}