{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-45014 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-45014 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-45014 is a critical SQL injection vulnerability in n/a, published on 14 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-45014 and fix it if it is affected.\n\nWhat it is: CVE-2021-45014 is a critical SQL injection vulnerability in n/a, published on 14 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-45014 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-2021-45014/ (Markdown: https://insights.sbomify.com/CVE-2021-45014/index.md)","id":"CVE-2021-45014","markdown":"https://insights.sbomify.com/CVE-2021-45014/index.md","name":"CVE-2021-45014","record":{"aliases":["GHSA-7957-q3ch-3v25"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"taocms","requires_auth":"none","summary":"An attacker can exploit a SQL injection vulnerability in the taocms background update 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":"taocms","vendor":"taogogo"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","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":"There is an upload sql injection vulnerability in the background of taocms 3.0.2 in parameter id:action=cms\u0026ctrl=update\u0026id=26","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-2021-45014","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Path traversal in n/a","id":"CVE-2021-45015"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2021-45010"},"products":["n/a"],"published":"2021-12-14","related":[{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2024-33350","kev_date_added":null,"published":"2024-04-29"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2022-48006","kev_date_added":null,"published":"2023-01-30"},{"cvss_score":9.8,"headline":"Server-side request forgery in n/a","id":"CVE-2022-46998","kev_date_added":null,"published":"2023-01-25"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2022-36262","kev_date_added":null,"published":"2022-08-15"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2022-23880","kev_date_added":null,"published":"2022-03-23"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-25505","kev_date_added":null,"published":"2022-03-21"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2022-25578","kev_date_added":null,"published":"2022-03-18"}],"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-04","vendors":["n/a"]},"summary":"An attacker can exploit a SQL injection vulnerability in the taocms background update parameter to read or modify database contents.","url":"https://insights.sbomify.com/CVE-2021-45014/"}