{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-16961 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-16961 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-16961 is a medium-severity SQL injection vulnerability in n/a, published on 27 Nov 2017. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-16961 and fix it if it is affected.\n\nWhat it is: CVE-2017-16961 is a medium-severity SQL injection vulnerability in n/a, published on 27 Nov 2017. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-16961 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-2017-16961/ (Markdown: https://insights.sbomify.com/CVE-2017-16961/index.md)","id":"CVE-2017-16961","markdown":"https://insights.sbomify.com/CVE-2017-16961/index.md","name":"CVE-2017-16961","record":{"aliases":["GHSA-hgqj-74jh-w3vh"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"BigTree CMS","requires_auth":"low_privilege","summary":"Authenticated attackers can exploit SQL injection in BigTree CMS to read database information via crafted tree approval requests.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"bigtree_cms","vendor":"bigtreecms"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"A SQL injection vulnerability in core/inc/auto-modules.php in BigTree CMS through 4.2.19 allows remote authenticated attackers to obtain information in the context of the user used by the application to retrieve data from the database. The attack uses an admin/trees/add/process request with a crafted _tags[] parameter that is mishandled in a later admin/ajax/dashboard/approve-change request.","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-2017-16961","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2017-16962"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2017-16960"},"products":["n/a"],"published":"2017-11-27","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2018-10574","kev_date_added":null,"published":"2018-04-30"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2017-9364","kev_date_added":null,"published":"2017-06-02"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2017-7695","kev_date_added":null,"published":"2017-04-11"},{"cvss_score":8.8,"headline":"SQL injection in n/a","id":"CVE-2020-26668","kev_date_added":null,"published":"2021-06-01"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2020-26670","kev_date_added":null,"published":"2021-06-01"},{"cvss_score":8.8,"headline":"SQL injection in n/a","id":"CVE-2017-11736","kev_date_added":null,"published":"2017-07-29"},{"cvss_score":8.8,"headline":"SQL injection in n/a","id":"CVE-2017-9449","kev_date_added":null,"published":"2017-06-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-08-05","vendors":["n/a"]},"summary":"Authenticated attackers can exploit SQL injection in BigTree CMS to read database information via crafted tree approval requests.","url":"https://insights.sbomify.com/CVE-2017-16961/"}