{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-25318 exists.","fix":"No fix has been published for CVE-2024-25318 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-25318 is a high-severity SQL injection vulnerability in n/a, published on 9 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-25318 and fix it if it is affected.\n\nWhat it is: CVE-2024-25318 is a high-severity SQL injection vulnerability in n/a, published on 9 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-25318 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-2024-25318/ (Markdown: https://insights.sbomify.com/CVE-2024-25318/index.md)","id":"CVE-2024-25318","markdown":"https://insights.sbomify.com/CVE-2024-25318/index.md","name":"CVE-2024-25318","record":{"aliases":["GHSA-5fm6-5hv6-6fjv"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Hotel Management System","requires_auth":"none","summary":"An attacker can execute arbitrary SQL commands via the 'pid' parameter in the print.php script, potentially accessing or modifying database contents.","user_interaction":"required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"hotel_management_system","vendor":"hotel_management_system_project"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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":"Code-projects Hotel Managment System 1.0 allows SQL Injection via the 'pid' parameter in Hotel/admin/print.php?pid=2.","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-2024-25318","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2024-25320"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2024-25316"},"products":["n/a"],"published":"2024-02-09","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-25314","kev_date_added":null,"published":"2024-02-09"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-25315","kev_date_added":null,"published":"2024-02-09"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-25316","kev_date_added":null,"published":"2024-02-09"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-28110","kev_date_added":null,"published":"2022-05-10"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2021-41651","kev_date_added":null,"published":"2021-10-04"},{"cvss_score":6.5,"headline":"SQL injection in n/a","id":"CVE-2022-48090","kev_date_added":null,"published":"2023-01-13"}],"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":"total"},"state":"PUBLISHED","updated":"2025-06-16","vendors":["n/a"]},"summary":"An attacker can execute arbitrary SQL commands via the 'pid' parameter in the print.php script, potentially accessing or modifying database contents.","url":"https://insights.sbomify.com/CVE-2024-25318/"}