{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-10106 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-10106 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-10106 is a critical SQL injection vulnerability in n/a, published on 5 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-10106 and fix it if it is affected.\n\nWhat it is: CVE-2020-10106 is a critical SQL injection vulnerability in n/a, published on 5 Mar 2020. 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-2020-10106 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-2020-10106/ (Markdown: https://insights.sbomify.com/CVE-2020-10106/index.md)","id":"CVE-2020-10106","markdown":"https://insights.sbomify.com/CVE-2020-10106/index.md","name":"CVE-2020-10106","record":{"aliases":["GHSA-xvvh-54m6-j663"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Daily Expense Tracker","requires_auth":"none","summary":"Attackers can inject SQL via email parameters to dump the database and bypass login in the Daily Expense Tracker System.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"daily_expense_tracker_system","vendor":"phpgurukul"}],"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":"PHPGurukul Daily Expense Tracker System 1.0 is vulnerable to SQL injection, as demonstrated by the email parameter in index.php or register.php. The SQL injection allows to dump the MySQL database and to bypass the login prompt.","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 in n/a","id":"CVE-2020-10106","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-10107"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2020-10105"},"products":["n/a"],"published":"2020-03-05","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-25349","kev_date_added":null,"published":"2025-02-12"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-25351","kev_date_added":null,"published":"2025-02-12"},{"cvss_score":6.9,"headline":"PHPGurukul Daily Expense Tracker System forgot-password.php sql injection","id":"CVE-2025-4907","kev_date_added":null,"published":"2025-05-19"},{"cvss_score":6.9,"headline":"PHPGurukul Daily Expense Tracker System expense-datewise-reports-detailed.php sql injection","id":"CVE-2025-4908","kev_date_added":null,"published":"2025-05-19"},{"cvss_score":6.9,"headline":"PHPGurukul Daily Expense Tracker System expense-monthwise-reports-detailed.php sql injection","id":"CVE-2025-4925","kev_date_added":null,"published":"2025-05-19"},{"cvss_score":6.9,"headline":"PHPGurukul Daily Expense Tracker System user-profile.php sql injection","id":"CVE-2025-4785","kev_date_added":null,"published":"2025-05-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":["n/a"]},"summary":"Attackers can inject SQL via email parameters to dump the database and bypass login in the Daily Expense Tracker System.","url":"https://insights.sbomify.com/CVE-2020-10106/"}