{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-2730 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-2730 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-2730 is a medium-severity authentication bypass vulnerability in Open-Emr Openemr, published on 9 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-2730 and fix it if it is affected.\n\nWhat it is: CVE-2022-2730 is a medium-severity authentication bypass vulnerability in Open-Emr Openemr, published on 9 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-2730 in the wild and no public exploit code.\n\nAffected product: Open-Emr Openemr. 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-2022-2730/ (Markdown: https://insights.sbomify.com/CVE-2022-2730/index.md)","id":"CVE-2022-2730","markdown":"https://insights.sbomify.com/CVE-2022-2730/index.md","name":"CVE-2022-2730","record":{"aliases":["GHSA-5jf7-8333-m22j"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenEMR medical software","requires_auth":"low_privilege","summary":"Attackers can bypass authorization controls via user-controlled keys to access or modify unauthorized patient data in OpenEMR.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntrdev","cpe":[{"product":"openemr","vendor":"open-emr"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"Authorization Bypass Through User-Controlled Key in GitHub repository openemr/openemr prior to 7.0.0.1.","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":"Authorization Bypass Through User-Controlled Key in openemr/openemr","id":"CVE-2022-2730","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"open-emr:openemr","products":["open-emr:openemr"],"type":"auth_bypass","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site Scripting (XSS) - Reflected in openemr/openemr","id":"CVE-2022-2731"},"packages":[],"prev":{"headline":"Cross-site Scripting (XSS) - DOM in openemr/openemr","id":"CVE-2022-2729"},"products":["openemr/openemr"],"published":"2022-08-09","related":[{"cvss_score":10,"headline":"OpenEMR has an Unauthenticated MedEx Token Disclosure","id":"CVE-2026-24898","kev_date_added":null,"published":"2026-03-03"},{"cvss_score":10,"headline":"OpenEMR Arbitrary File Read Vulnerability","id":"CVE-2026-24849","kev_date_added":null,"published":"2026-02-25"},{"cvss_score":10,"headline":"OpenEMR has SQL Injection in Patient API Sort Parameter","id":"CVE-2026-24908","kev_date_added":null,"published":"2026-02-25"},{"cvss_score":10,"headline":"Improper Restriction of Rendered UI Layers or Frames in openemr/openemr","id":"CVE-2022-2734","kev_date_added":null,"published":"2022-08-09"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-22611","kev_date_added":null,"published":"2025-04-03"},{"cvss_score":9.8,"headline":"Privilege escalation in n/a","id":"CVE-2024-37734","kev_date_added":null,"published":"2024-06-26"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2019-17197","kev_date_added":null,"published":"2019-10-05"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["openemr"]},"summary":"Attackers can bypass authorization controls via user-controlled keys to access or modify unauthorized patient data in OpenEMR.","url":"https://insights.sbomify.com/CVE-2022-2730/"}