{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-64064 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-64064 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-64064 is a high-severity vulnerability in n/a, published on 25 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-64064 and fix it if it is affected.\n\nWhat it is: CVE-2025-64064 is a high-severity vulnerability in n/a, published on 25 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-64064 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-64064/ (Markdown: https://insights.sbomify.com/CVE-2025-64064/index.md)","id":"CVE-2025-64064","markdown":"https://insights.sbomify.com/CVE-2025-64064/index.md","name":"CVE-2025-64064","record":{"aliases":["GHSA-qmvr-pxjf-gcmg"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Primakon Pi Portal","requires_auth":"low_privilege","summary":"Low-level users can escalate privileges to Administrator by modifying their security profile ID via an insecure API endpoint.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"project_contract_management","vendor":"primakon"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"Primakon Pi Portal 1.0.18 /api/v2/pp_users endpoint fails to adequately check user permissions before processing a PATCH request to modify the PP_SECURITY_PROFILE_ID. Because of weak access controls any low level user can use this API and change their permission to Administrator by using PP_SECURITY_PROFILE_ID=2 inside body of request and escalate privileges.","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":"Privilege escalation in n/a","id":"CVE-2025-64064","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Auth bypass in n/a","id":"CVE-2025-64065"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2025-64063"},"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":"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":5.3,"headline":"Missing authorization in n/a","id":"CVE-2025-64067","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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-11-25","vendors":["n/a"]},"summary":"Low-level users can escalate privileges to Administrator by modifying their security profile ID via an insecure API endpoint.","url":"https://insights.sbomify.com/CVE-2025-64064/"}