{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25349 exists.","fix":"No fix has been published for CVE-2025-25349 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-25349 is a critical SQL injection vulnerability in n/a, published on 12 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-25349 and fix it if it is affected.\n\nWhat it is: CVE-2025-25349 is a critical SQL injection vulnerability in n/a, published on 12 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25349 exists.\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-2025-25349/ (Markdown: https://insights.sbomify.com/CVE-2025-25349/index.md)","id":"CVE-2025-25349","markdown":"https://insights.sbomify.com/CVE-2025-25349/index.md","name":"CVE-2025-25349","record":{"aliases":["GHSA-qv4j-f75x-4v5x"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Daily Expense Tracker","requires_auth":"none","summary":"An attacker can inject SQL commands via the costitem parameter to read or modify database contents 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":"cisa-adp","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 v1.1 is vulnerable to SQL Injection in /dets/add-expense.php via the costitem parameter.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"SQL injection in n/a","id":"CVE-2025-25349","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2025-25351"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2025-25343"},"products":["n/a"],"published":"2025-02-12","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-25351","kev_date_added":null,"published":"2025-02-12"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2020-10106","kev_date_added":null,"published":"2020-03-05"},{"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-03-05","vendors":["n/a"]},"summary":"An attacker can inject SQL commands via the costitem parameter to read or modify database contents in the Daily Expense Tracker System.","url":"https://insights.sbomify.com/CVE-2025-25349/"}