{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-19898 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-19898 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-19898 is a high-severity SQL injection vulnerability in n/a, published on 6 Dec 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-19898 and fix it if it is affected.\n\nWhat it is: CVE-2018-19898 is a high-severity SQL injection vulnerability in n/a, published on 6 Dec 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-19898 in the wild and no public exploit code.\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-2018-19898/ (Markdown: https://insights.sbomify.com/CVE-2018-19898/index.md)","id":"CVE-2018-19898","markdown":"https://insights.sbomify.com/CVE-2018-19898/index.md","name":"CVE-2018-19898","record":{"aliases":["GHSA-6598-2m88-f7xr"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"ThinkCMF CMS","requires_auth":"low_privilege","summary":"Authenticated users can execute SQL injection attacks via the article edit function in ThinkCMF, potentially reading or modifying database contents.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"thinkcmf","vendor":"thinkcmf"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"ThinkCMF X2.2.2 has SQL Injection via the method edit_post in ArticleController.class.php and is exploitable by normal authenticated users via the post[id][1] parameter in an article edit_post action.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"SQL injection in n/a","id":"CVE-2018-19898","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-19901"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2018-19897"},"products":["n/a"],"published":"2018-12-06","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2024-31615","kev_date_added":null,"published":"2024-04-25"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2020-20601","kev_date_added":null,"published":"2021-12-22"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2019-6713","kev_date_added":null,"published":"2019-01-23"},{"cvss_score":8.8,"headline":"ThinkCMF Cross Site Request Forgery (CSRF) vulnerability","id":"CVE-2022-40489","kev_date_added":null,"published":"2022-12-01"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2019-7580","kev_date_added":null,"published":"2019-02-07"},{"cvss_score":7.2,"headline":"SQL injection in n/a","id":"CVE-2018-19894","kev_date_added":null,"published":"2018-12-06"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["n/a"]},"summary":"Authenticated users can execute SQL injection attacks via the article edit function in ThinkCMF, potentially reading or modifying database contents.","url":"https://insights.sbomify.com/CVE-2018-19898/"}