{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-4595 exists.","fix":"No fix has been published for CVE-2024-4595 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-4595 is a medium-severity SQL injection vulnerability in Sem-Cms Semcms, published on 7 May 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-4595 and fix it if it is affected.\n\nWhat it is: CVE-2024-4595 is a medium-severity SQL injection vulnerability in Sem-Cms Semcms, published on 7 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-4595 exists.\n\nAffected product: Sem-Cms Semcms. 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-4595/ (Markdown: https://insights.sbomify.com/CVE-2024-4595/index.md)","id":"CVE-2024-4595","markdown":"https://insights.sbomify.com/CVE-2024-4595/index.md","name":"CVE-2024-4595","record":{"aliases":["GHSA-v5vq-p7x3-f239"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"SEMCMS","requires_auth":"low_privilege","summary":"Remote attackers can exploit SQL injection in SEMCMS to read or modify database contents via the locate function.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"semcms","vendor":"sem-cms"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"A vulnerability has been found in SEMCMS up to 4.8 and classified as critical. Affected by this vulnerability is the function locate of the file function.php. The manipulation leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-263317 was assigned to this vulnerability.","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":"SEMCMS function.php locate sql injection","id":"CVE-2024-4595","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"sem-cms:semcms","products":["sem-cms:semcms"],"type":"sql_injection","year":"2024"},"n_packages":0,"n_references":4,"next":{"headline":"Kimai Session information disclosure","id":"CVE-2024-4596"},"packages":[],"prev":{"headline":"DedeCMS sys_safe.php cross-site request forgery","id":"CVE-2024-4594"},"products":["SEMCMS"],"published":"2024-05-07","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-25686","kev_date_added":null,"published":"2025-03-27"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-46103","kev_date_added":null,"published":"2024-09-20"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-30938","kev_date_added":null,"published":"2024-04-18"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2024-31012","kev_date_added":null,"published":"2024-04-03"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-25422","kev_date_added":null,"published":"2024-02-28"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2023-50563","kev_date_added":null,"published":"2023-12-14"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2023-37647","kev_date_added":null,"published":"2023-07-31"}],"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-08-01","vendors":["n/a"]},"summary":"Remote attackers can exploit SQL injection in SEMCMS to read or modify database contents via the locate function.","url":"https://insights.sbomify.com/CVE-2024-4595/"}