{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63718 exists.","fix":"No fix has been published for CVE-2025-63718 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-63718 is a medium-severity SQL injection vulnerability in n/a, published on 7 Nov 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-63718 and fix it if it is affected.\n\nWhat it is: CVE-2025-63718 is a medium-severity SQL injection vulnerability in n/a, published on 7 Nov 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-63718 exists.\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-2025-63718/ (Markdown: https://insights.sbomify.com/CVE-2025-63718/index.md)","id":"CVE-2025-63718","markdown":"https://insights.sbomify.com/CVE-2025-63718/index.md","name":"CVE-2025-63718","record":{"aliases":["GHSA-745r-657p-6h6w"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Patient Queue Management System","requires_auth":"none","summary":"Attackers can execute arbitrary SQL commands via the appointmentID parameter in the api_patient_schedule.php endpoint of the Patient Queue Management System.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"patients_waiting_area_queue_management_system","vendor":"pamzey"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"A SQL injection vulnerability exists in the SourceCodester PQMS (Patient Queue Management System) 1.0 in the api_patient_schedule.php endpoint. The appointmentID parameter is not properly sanitized, allowing attackers to execute arbitrary SQL commands.","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":"SQL injection in n/a","id":"CVE-2025-63718","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"SQL injection in n/a","id":"CVE-2025-63719"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2025-63717"},"products":["n/a"],"published":"2025-11-07","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-64081","kev_date_added":null,"published":"2025-12-08"},{"cvss_score":6.9,"headline":"SourceCodester Patients Waiting Area Queue Management System patient-search.php improper authorization","id":"CVE-2026-3817","kev_date_added":null,"published":"2026-03-09"},{"cvss_score":6.9,"headline":"SourceCodester Patients Waiting Area Queue Management System api_patient_schedule.php sql injection","id":"CVE-2025-13248","kev_date_added":null,"published":"2025-11-16"},{"cvss_score":6.9,"headline":"SQL injection in Patients Waiting Area Queue Management System","id":"CVE-2025-13122","kev_date_added":null,"published":"2025-11-13"},{"cvss_score":5.3,"headline":"SourceCodester Patients Waiting Area Queue Management System checkin.php improper authorization","id":"CVE-2026-3724","kev_date_added":null,"published":"2026-03-08"},{"cvss_score":5.3,"headline":"SourceCodester/Patrick Mvuma Patients Waiting Area Queue Management System appointments.php cross site scripting","id":"CVE-2026-2149","kev_date_added":null,"published":"2026-02-08"}],"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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-11-12","vendors":["n/a"]},"summary":"Attackers can execute arbitrary SQL commands via the appointmentID parameter in the api_patient_schedule.php endpoint of the Patient Queue Management System.","url":"https://insights.sbomify.com/CVE-2025-63718/"}