{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-25400 exists.","fix":"No fix has been published for CVE-2024-25400 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-25400 is a critical SQL injection vulnerability in n/a, published on 27 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-25400 and fix it if it is affected.\n\nWhat it is: CVE-2024-25400 is a critical SQL injection vulnerability in n/a, published on 27 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-25400 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-25400/ (Markdown: https://insights.sbomify.com/CVE-2024-25400/index.md)","id":"CVE-2024-25400","markdown":"https://insights.sbomify.com/CVE-2024-25400/index.md","name":"CVE-2024-25400","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Subrion CMS","requires_auth":"none","summary":"Reported SQL injection in Subrion CMS is disputed as the vulnerable code path does not exist, but if valid, it allows database manipulation.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"subrion","vendor":"intelliants"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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":"Subrion CMS 4.2.1 is vulnerable to SQL Injection via ia.core.mysqli.php. NOTE: this is disputed by multiple third parties because it refers to an HTTP request to a PHP file that only contains a class, without any mechanism for accepting external input, and the reportedly vulnerable method is not present in the file.","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":"SQL injection in n/a","id":"CVE-2024-25400","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":"Business logic in n/a","id":"CVE-2024-25407"},"packages":[],"prev":{"headline":"Subrion CMS vulnerable to Cross Site Scripting","id":"CVE-2024-25399"},"products":["n/a"],"published":"2024-02-27","related":[{"cvss_score":9.8,"headline":"SQL Injection in Subrion CMS","id":"CVE-2020-18155","kev_date_added":null,"published":"2021-07-14"},{"cvss_score":9.8,"headline":"Subrion CMS PHP Object Injection","id":"CVE-2017-5543","kev_date_added":null,"published":"2017-01-20"},{"cvss_score":8.8,"headline":"Subrion remote command execution vulnerability","id":"CVE-2023-46947","kev_date_added":null,"published":"2023-11-03"},{"cvss_score":8.8,"headline":"Subrion CMS CSRF Vulnerability","id":"CVE-2018-21037","kev_date_added":null,"published":"2020-03-17"},{"cvss_score":8.8,"headline":"Subrion CMS CSRF Vulnerability","id":"CVE-2017-15063","kev_date_added":null,"published":"2017-10-06"},{"cvss_score":8.1,"headline":"Subrion CMS Cross-Site Request Forgery (CSRF) vulnerability","id":"CVE-2019-20390","kev_date_added":null,"published":"2020-05-15"}],"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":"2025-05-15","vendors":["n/a"]},"summary":"Reported SQL injection in Subrion CMS is disputed as the vulnerable code path does not exist, but if valid, it allows database manipulation.","url":"https://insights.sbomify.com/CVE-2024-25400/"}