{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-43851 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-43851 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-43851 is a high-severity SQL injection vulnerability in anuko timetracker, published on 21 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-43851 and fix it if it is affected.\n\nWhat it is: CVE-2021-43851 is a high-severity SQL injection vulnerability in anuko timetracker, published on 21 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-43851 in the wild and no public exploit code.\n\nAffected product: anuko timetracker. 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-43851/ (Markdown: https://insights.sbomify.com/CVE-2021-43851/index.md)","id":"CVE-2021-43851","markdown":"https://insights.sbomify.com/CVE-2021-43851/index.md","name":"CVE-2021-43851","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Time tracking application","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary SQL commands via unvalidated group and status parameters in Anuko Time Tracker, potentially accessing or modifying data.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"time_tracker","vendor":"anuko"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"Anuko Time Tracker is an open source, web-based time tracking application written in PHP. SQL injection vulnerability exist in multiple files in Time Tracker version 1.19.33.5606 and prior due to not properly checking of the \"group\" and \"status\" parameters in POST requests. Group parameter is posted along when navigating between organizational subgroups (groups.php file). Status parameter is used in multiple files to change a status of an entity such as making a project, task, or user inactive. This issue has been patched in version 1.19.33.5607. An upgrade is highly recommended. If an upgrade is not practical, introduce ttValidStatus function as in the latest version and start using it user input check blocks wherever status field is used. For groups.php fix, introduce ttValidInteger function as in the latest version and use it in the access check block in the file.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"SQL injection vulnerability in anuko timetracker","id":"CVE-2021-43851","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2021"},"n_packages":0,"n_references":3,"next":{"headline":"JavaScript Prototype Pollution in oro/platform","id":"CVE-2021-43852"},"packages":[],"prev":{"headline":"Denial of Service in discourse","id":"CVE-2021-43850"},"products":["timetracker"],"published":"2021-12-21","related":[{"cvss_score":9.8,"headline":"Business logic in n/a","id":"CVE-2020-27422","kev_date_added":null,"published":"2020-11-16"},{"cvss_score":8.8,"headline":"Time Tracker has Blind SQL Injection Vulnerability in Reports","id":"CVE-2023-32306","kev_date_added":null,"published":"2023-05-12"},{"cvss_score":8.7,"headline":"CSV injection in Anuko Time Tracker","id":"CVE-2020-15255","kev_date_added":null,"published":"2020-10-16"},{"cvss_score":8.2,"headline":"SQL Injection Vulnerability in anuko timetracker","id":"CVE-2023-32308","kev_date_added":null,"published":"2023-05-15"},{"cvss_score":8.1,"headline":"Reflected XSS vulnerability in time.php","id":"CVE-2021-41139","kev_date_added":null,"published":"2021-10-13"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2020-27423","kev_date_added":null,"published":"2020-11-16"}],"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":["anuko"]},"summary":"Attackers can execute arbitrary SQL commands via unvalidated group and status parameters in Anuko Time Tracker, potentially accessing or modifying data.","url":"https://insights.sbomify.com/CVE-2021-43851/"}