{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59686 exists.","fix":"No fix has been published for CVE-2025-59686 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-59686 is a medium-severity missing authorization vulnerability in n/a, published on 1 Oct 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-59686 and fix it if it is affected.\n\nWhat it is: CVE-2025-59686 is a medium-severity missing authorization vulnerability in n/a, published on 1 Oct 2025. 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-2025-59686 exists.\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-59686/ (Markdown: https://insights.sbomify.com/CVE-2025-59686/index.md)","id":"CVE-2025-59686","markdown":"https://insights.sbomify.com/CVE-2025-59686/index.md","name":"CVE-2025-59686","record":{"aliases":["GHSA-hrcp-jqfc-jx4p"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Kazaar API","requires_auth":"none","summary":"Attackers can access or modify documents for arbitrary orders by manipulating the order ID in API requests, bypassing authorization checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"}],"description":"Kazaar 1.25.12 allows /api/v1/org-id/orders/order-id/documents calls with a modified order-id.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Missing authorization in n/a","id":"CVE-2025-59686","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2025-59687"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2025-59685"},"products":["n/a"],"published":"2025-10-01","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-28","vendors":["n/a"]},"summary":"Attackers can access or modify documents for arbitrary orders by manipulating the order ID in API requests, bypassing authorization checks.","url":"https://insights.sbomify.com/CVE-2025-59686/"}