{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-64067 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-64067 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-64067 is a medium-severity missing authorization vulnerability in n/a, published on 25 Nov 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-64067 and fix it if it is affected.\n\nWhat it is: CVE-2025-64067 is a medium-severity missing authorization vulnerability in n/a, published on 25 Nov 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-64067 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-64067/ (Markdown: https://insights.sbomify.com/CVE-2025-64067/index.md)","id":"CVE-2025-64067","markdown":"https://insights.sbomify.com/CVE-2025-64067/index.md","name":"CVE-2025-64067","record":{"aliases":["GHSA-mf87-r67v-2m82"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Primakon Pi Portal","requires_auth":"none","summary":"Attackers can access other users' data or entire datasets by manipulating IDs or omitting filters due to missing server-side authorization checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"project_contract_management","vendor":"primakon"}],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"Primakon Pi Portal 1.0.18 API endpoints responsible for retrieving object-specific or filtered data (e.g., user profiles, project records) fail to implement sufficient server-side validation to confirm that the requesting user is authorized to access the requested object or dataset. This vulnerability can be exploited in two ways: Direct ID manipulation and IDOR, by changing an ID parameter (e.g., user_id, project_id) in the request, an attacker can access the object and data belonging to another user; and filter Omission, by omitting the filtering parameter entirely, an attacker can cause the endpoint to return an entire unfiltered dataset of all stored records for all users. This flaw leads to the unauthorized exposure of sensitive personal and organizational information.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Missing authorization in n/a","id":"CVE-2025-64067","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":"Cross-site scripting in n/a","id":"CVE-2025-64070"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2025-64066"},"products":["n/a"],"published":"2025-11-25","related":[{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2025-64063","kev_date_added":null,"published":"2025-11-25"},{"cvss_score":8.8,"headline":"Auth bypass in n/a","id":"CVE-2025-64062","kev_date_added":null,"published":"2025-11-25"},{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2025-64064","kev_date_added":null,"published":"2025-11-25"},{"cvss_score":8.8,"headline":"Auth bypass in n/a","id":"CVE-2025-64065","kev_date_added":null,"published":"2025-11-25"},{"cvss_score":8.6,"headline":"Missing authorization in n/a","id":"CVE-2025-64066","kev_date_added":null,"published":"2025-11-25"},{"cvss_score":4.3,"headline":"Missing authorization in n/a","id":"CVE-2025-64061","kev_date_added":null,"published":"2025-11-25"}],"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-11-25","vendors":["n/a"]},"summary":"Attackers can access other users' data or entire datasets by manipulating IDs or omitting filters due to missing server-side authorization checks.","url":"https://insights.sbomify.com/CVE-2025-64067/"}