{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-124483 exists.","exposure":"","fix":"No fix has been published for CVE-2026-124483 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-124483 is a high-severity vulnerability in openemr, published on 8 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-124483 and fix it if it is affected.\n\nWhat it is: CVE-2026-124483 is a high-severity vulnerability in openemr, published on 8 Nov 2026. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-124483 exists.\n\nAffected product: 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-2026-124483/ (Markdown: https://insights.sbomify.com/CVE-2026-124483/index.md)","id":"CVE-2026-124483","markdown":"https://insights.sbomify.com/CVE-2026-124483/index.md","name":"CVE-2026-124483","record":{"aliases":["GHSA-qrc2-5wvq-f68q","GHSA-vwmc-g4gv-2mf9"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"OpenEMR before 8.4.0 contains an incorrect authorization vulnerability because the prescription REST API routes check the patients.med ACL instead of patients.rx and request no specific permission bit, so read-only Medical/History access passes the check. Authenticated staff users can reuse the UI-exposed APICSRFTOKEN to enumerate prescription UUIDs, forge prescriptions for arbitrary patients, and deactivate existing prescriptions tenant-wide.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"OpenEMR before 8.4.0 Improper Authorization via Prescription REST API","id":"CVE-2026-124483","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"OpenEMR before 8.4.0 Missing Authorization in Portal Onsite-Document APIs","id":"CVE-2026-124484"},"nickname":null,"packages":[],"prev":{"headline":"OpenEMR before 8.4.0 Cross-Patient PHI Exfiltration via SMART Patient Launch","id":"CVE-2026-124482"},"products":["openemr"],"published":"2026-11-08","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":"total"},"state":"PUBLISHED","updated":"2026-11-09","vendors":["openemr"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-124483/"}