{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-65781 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-65781 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-65781 is a high-severity denial of service vulnerability in n/a, published on 15 Dec 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-65781 and fix it if it is affected.\n\nWhat it is: CVE-2025-65781 is a high-severity denial of service vulnerability in n/a, published on 15 Dec 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-65781 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-65781/ (Markdown: https://insights.sbomify.com/CVE-2025-65781/index.md)","id":"CVE-2025-65781","markdown":"https://insights.sbomify.com/CVE-2025-65781/index.md","name":"CVE-2025-65781","record":{"aliases":["GHSA-j27j-25gc-gv9v"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["denial_of_service","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Wekan kanban board","requires_auth":"none","summary":"Attackers can cause denial of service and potential identity spoofing by sending non-empty bearer tokens to the attachment upload API.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wekan","vendor":"wekan_project"}],"cvss":{"score":8.2,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"An issue was discovered in Wekan The Open Source kanban board system up to version 18.15, fixed in 18.16. Attachment upload API treats the Authorization bearer value as a userId and enters a non-terminating body-handling branch for any non-empty bearer token, enabling trivial application-layer DoS and latent identity-spoofing.","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":"Denial of service in n/a","id":"CVE-2025-65781","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Missing authorization in n/a","id":"CVE-2025-65782"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2025-65780"},"products":["n/a"],"published":"2025-12-15","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"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-16","vendors":["n/a"]},"summary":"Attackers can cause denial of service and potential identity spoofing by sending non-empty bearer tokens to the attachment upload API.","url":"https://insights.sbomify.com/CVE-2025-65781/"}