{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-70063 exists.","fix":"No fix has been published for CVE-2025-70063 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-70063 is a medium-severity vulnerability in Phpgurukul Hospital Management System, published on 18 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-70063 and fix it if it is affected.\n\nWhat it is: CVE-2025-70063 is a medium-severity vulnerability in Phpgurukul Hospital Management System, published on 18 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-70063 exists.\n\nAffected product: Phpgurukul Hospital Management System. 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-70063/ (Markdown: https://insights.sbomify.com/CVE-2025-70063/index.md)","id":"CVE-2025-70063","markdown":"https://insights.sbomify.com/CVE-2025-70063/index.md","name":"CVE-2025-70063","record":{"aliases":["GHSA-8gfj-223w-87pr"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Hospital Management System","requires_auth":"low_privilege","summary":"An attacker can access other patients' confidential medical records by manipulating the viewid parameter in the Medical History module.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"hospital_management_system","vendor":"phpgurukul"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"The 'Medical History' module in PHPGurukul Hospital Management System v4.0 contains an Insecure Direct Object Reference (IDOR) vulnerability. The application fails to verify that the requested 'viewid' parameter belongs to the currently authenticated patient. This allows a user to access the confidential medical records of other patients by iterating the 'viewid' integer.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2025-70063","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"phpgurukul:hospital_management_system","products":["phpgurukul:hospital_management_system"],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2025-70064"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2025-70062"},"products":["n/a"],"published":"2026-02-18","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-56212","kev_date_added":null,"published":"2025-08-25"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-56214","kev_date_added":null,"published":"2025-08-25"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2024-51360","kev_date_added":null,"published":"2025-05-23"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2020-26629","kev_date_added":null,"published":"2024-01-10"},{"cvss_score":9.8,"headline":"Privilege escalation in n/a","id":"CVE-2023-31498","kev_date_added":null,"published":"2023-05-11"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-24263","kev_date_added":null,"published":"2022-01-31"},{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2025-70064","kev_date_added":null,"published":"2026-02-18"}],"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":"2026-02-18","vendors":["n/a"]},"summary":"An attacker can access other patients' confidential medical records by manipulating the viewid parameter in the Medical History module.","url":"https://insights.sbomify.com/CVE-2025-70063/"}