{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-39852 exists.","fix":"No fix has been published for CVE-2023-39852 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-39852 is a critical SQL injection vulnerability in n/a, published on 15 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-39852 and fix it if it is affected.\n\nWhat it is: CVE-2023-39852 is a critical SQL injection vulnerability in n/a, published on 15 Aug 2023. 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-2023-39852 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-2023-39852/ (Markdown: https://insights.sbomify.com/CVE-2023-39852/index.md)","id":"CVE-2023-39852","markdown":"https://insights.sbomify.com/CVE-2023-39852/index.md","name":"CVE-2023-39852","record":{"aliases":["GHSA-ffcp-3x2p-58h7"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"DoctorMMS web app","requires_auth":"none","summary":"SQL injection in DoctorMMS allows attackers to manipulate database queries via the userid parameter, potentially exposing or altering data.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"doctor_appointment_system","vendor":"doctor_appointment_system_project"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"Doctormms v1.0 was discovered to contain a SQL injection vulnerability via the $userid parameter at myAppoinment.php. NOTE: this is disputed by a third party who claims that the userid is a session variable controlled by the server, and thus cannot be used for exploitation. The original reporter counterclaims that this originates from $_SESSION[\"userid\"]=$_POST[\"userid\"] at line 68 in doctors\\doctorlogin.php, where userid under POST is not a session variable controlled by the server.","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-2023-39852","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"SQL injection in n/a","id":"CVE-2023-39853"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2023-39851"},"products":["n/a"],"published":"2023-08-15","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2023-40945","kev_date_added":null,"published":"2023-09-11"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2021-27314","kev_date_added":null,"published":"2021-03-04"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2021-27315","kev_date_added":null,"published":"2021-03-24"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2021-27316","kev_date_added":null,"published":"2021-03-24"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2021-27319","kev_date_added":null,"published":"2021-03-24"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2021-27320","kev_date_added":null,"published":"2021-03-24"}],"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":"2024-08-02","vendors":["n/a"]},"summary":"SQL injection in DoctorMMS allows attackers to manipulate database queries via the userid parameter, potentially exposing or altering data.","url":"https://insights.sbomify.com/CVE-2023-39852/"}