{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-9789 exists.","fix":"No fix has been published for CVE-2024-9789 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-9789 is a medium-severity SQL injection vulnerability in LyLme_spage, published on 10 Oct 2024. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-9789 and fix it if it is affected.\n\nWhat it is: CVE-2024-9789 is a medium-severity SQL injection vulnerability in LyLme_spage, published on 10 Oct 2024. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-9789 exists.\n\nAffected product: LyLme_spage. 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-9789/ (Markdown: https://insights.sbomify.com/CVE-2024-9789/index.md)","id":"CVE-2024-9789","markdown":"https://insights.sbomify.com/CVE-2024-9789/index.md","name":"CVE-2024-9789","record":{"aliases":["GHSA-6qmr-jh3v-q6rr"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"LyLme_spage CMS","requires_auth":"high_privilege","summary":"Remote attackers can exploit SQL injection in the admin apply.php file to read or modify database contents.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"lylme_spage","vendor":"lylme"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/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":"A vulnerability was found in LyLme_spage 1.9.5 and classified as critical. This issue affects some unknown processing of the file /admin/apply.php. The manipulation of the argument id leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"LyLme_spage apply.php sql injection","id":"CVE-2024-9789","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2024"},"n_packages":0,"n_references":4,"next":{"headline":"LyLme_spage sou.php sql injection","id":"CVE-2024-9790"},"packages":[],"prev":{"headline":"LyLme_spage tag.php sql injection","id":"CVE-2024-9788"},"products":["LyLme_spage"],"published":"2024-10-10","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2024-48176","kev_date_added":null,"published":"2024-11-05"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-48356","kev_date_added":null,"published":"2024-10-28"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-48357","kev_date_added":null,"published":"2024-10-28"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2024-34982","kev_date_added":null,"published":"2024-05-17"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2023-45951","kev_date_added":null,"published":"2023-10-17"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2023-45952","kev_date_added":null,"published":"2023-10-17"},{"cvss_score":9.1,"headline":"Server-side request forgery in n/a","id":"CVE-2024-36675","kev_date_added":null,"published":"2024-06-04"}],"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":"2024-10-10","vendors":["n/a"]},"summary":"Remote attackers can exploit SQL injection in the admin apply.php file to read or modify database contents.","url":"https://insights.sbomify.com/CVE-2024-9789/"}