{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-34320 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-34320 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-34320 is a critical missing authorization vulnerability in n/a, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-34320 and fix it if it is affected.\n\nWhat it is: CVE-2024-34320 is a critical missing authorization vulnerability in n/a, published on 13 Oct 2026. 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-2024-34320 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-2024-34320/ (Markdown: https://insights.sbomify.com/CVE-2024-34320/index.md)","id":"CVE-2024-34320","markdown":"https://insights.sbomify.com/CVE-2024-34320/index.md","name":"CVE-2024-34320","record":{"aliases":["GHSA-679h-cxq5-8mcv"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Law RMS","requires_auth":"none","summary":"Attackers can access sensitive API endpoints without proper authorization, potentially reading or modifying data in ProPhoenix Law RMS.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"ProPhoenix Law RMS v2022.2403.3.101 was discovered to contain an incorrect access control issue in sensitive API endpoints.","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-2024-34320","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2024-34321"},"packages":[],"prev":{"headline":"Server-side request forgery in n/a","id":"CVE-2024-34319"},"products":["n/a"],"published":"2026-10-13","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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-14","vendors":["n/a"]},"summary":"Attackers can access sensitive API endpoints without proper authorization, potentially reading or modifying data in ProPhoenix Law RMS.","url":"https://insights.sbomify.com/CVE-2024-34320/"}