{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-40617 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-40617 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-40617 is a critical SQL injection vulnerability in Bookgy, published on 29 Apr 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-40617 and fix it if it is affected.\n\nWhat it is: CVE-2025-40617 is a critical SQL injection vulnerability in Bookgy, published on 29 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-40617 in the wild and no public exploit code.\n\nAffected product: Bookgy. 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-40617/ (Markdown: https://insights.sbomify.com/CVE-2025-40617/index.md)","id":"CVE-2025-40617","markdown":"https://insights.sbomify.com/CVE-2025-40617/index.md","name":"CVE-2025-40617","record":{"aliases":["GHSA-v836-66v3-26j5"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Bookgy web application","requires_auth":"none","summary":"Attackers can manipulate database contents via SQL injection in Bookgy's AJAX endpoint, requiring immediate attention from system administrators.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"INCIBE","cpe":[{"product":"bookgy","vendor":"bookgy"}],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"SQL injection vulnerability in Bookgy. This vulnerability could allow an attacker to retrieve, create, update and delete databases by sending an HTTP request through the \"IDTIPO\", \"IDPISTA\" and \"IDSOCIO\" parameters in /bkg_seleccionar_hora_ajax.php.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"SQL injection vulnerability in Bookgy","id":"CVE-2025-40617","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection vulnerability in Bookgy","id":"CVE-2025-40618"},"packages":[],"prev":{"headline":"Reflected Cross-Site Scripting (XSS) vulnerability in Bookgy","id":"CVE-2025-40616"},"products":["Bookgy"],"published":"2025-04-29","related":[{"cvss_score":9.3,"headline":"SQL injection vulnerability in Bookgy","id":"CVE-2025-40618","kev_date_added":null,"published":"2025-04-29"},{"cvss_score":9.3,"headline":"Improper access control vulnerability in Bookgy","id":"CVE-2025-40619","kev_date_added":null,"published":"2025-04-29"},{"cvss_score":5.1,"headline":"Reflected Cross-Site Scripting (XSS) vulnerability in Bookgy","id":"CVE-2025-40615","kev_date_added":null,"published":"2025-04-29"},{"cvss_score":5.1,"headline":"Reflected Cross-Site Scripting (XSS) vulnerability in Bookgy","id":"CVE-2025-40616","kev_date_added":null,"published":"2025-04-29"}],"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-29","vendors":["Bookgy"]},"summary":"Attackers can manipulate database contents via SQL injection in Bookgy's AJAX endpoint, requiring immediate attention from system administrators.","url":"https://insights.sbomify.com/CVE-2025-40617/"}