{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-51659 exists.","fix":"No fix has been published for CVE-2025-51659 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-51659 is a medium-severity SQL injection vulnerability in Sem-Cms Semcms, published on 14 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-51659 and fix it if it is affected.\n\nWhat it is: CVE-2025-51659 is a medium-severity SQL injection vulnerability in Sem-Cms Semcms, published on 14 Jul 2025. 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-2025-51659 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-2025-51659/ (Markdown: https://insights.sbomify.com/CVE-2025-51659/index.md)","id":"CVE-2025-51659","markdown":"https://insights.sbomify.com/CVE-2025-51659/index.md","name":"CVE-2025-51659","record":{"aliases":["GHSA-5v4f-89m5-g4mw"],"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 CMS","requires_auth":"low_privilege","summary":"Attackers can exploit SQL injection in SemCms via the ID parameter to read or modify database contents.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"semcms","vendor":"sem-cms"}],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"SemCms v5.0 was discovered to contain a SQL injection vulnerability via the ID parameter at SEMCMS_Products.php.","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-2025-51659","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"sem-cms:semcms","products":["sem-cms:semcms"],"type":"sql_injection","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"SQL injection in n/a","id":"CVE-2025-51660"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2025-51658"},"products":["n/a"],"published":"2025-07-14","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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-05","vendors":["n/a"]},"summary":"Attackers can exploit SQL injection in SemCms via the ID parameter to read or modify database contents.","url":"https://insights.sbomify.com/CVE-2025-51659/"}