{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-31117 exists.","fix":"No fix has been published for CVE-2025-31117 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-31117 is a medium-severity server-side request forgery vulnerability in Open-Emr Openemr, published on 31 Mar 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-31117 and fix it if it is affected.\n\nWhat it is: CVE-2025-31117 is a medium-severity server-side request forgery vulnerability in Open-Emr Openemr, published on 31 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-31117 exists.\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-2025-31117/ (Markdown: https://insights.sbomify.com/CVE-2025-31117/index.md)","id":"CVE-2025-31117","markdown":"https://insights.sbomify.com/CVE-2025-31117/index.md","name":"CVE-2025-31117","record":{"aliases":["GHSA-2pvv-ph3x-2f9h"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenEMR EHR","requires_auth":"none","summary":"Attackers can force the OpenEMR server to make unauthorized external requests, potentially exfiltrating sensitive information via DNS or HTTP interactions.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"openemr","vendor":"open-emr"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"OpenEMR is a free and open source electronic health records and medical practice management application. An Out-of-Band Server-Side Request Forgery (OOB SSRF) vulnerability was identified in OpenEMR, allowing an attacker to force the server to make unauthorized requests to external or internal resources. this attack does not return a direct response but can be exploited through DNS or HTTP interactions to exfiltrate sensitive information. This vulnerability is fixed in 7.0.3.1.","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 Out-of-Band Server-Side Request Forgery (OOB SSRF) Vulnerability","id":"CVE-2025-31117","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"open-emr:openemr","products":["open-emr:openemr"],"type":"ssrf","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"NamelessMC Has Forum Reply Submission Time Limit Bypass","id":"CVE-2025-31118"},"packages":[],"prev":{"headline":"Mobile Security Framework (MobSF) has a SSRF Vulnerability fix bypass on assetlinks_check with DNS Rebinding","id":"CVE-2025-31116"},"products":["openemr"],"published":"2025-03-31","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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-31","vendors":["openemr"]},"summary":"Attackers can force the OpenEMR server to make unauthorized external requests, potentially exfiltrating sensitive information via DNS or HTTP interactions.","url":"https://insights.sbomify.com/CVE-2025-31117/"}