{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8134 exists.","fix":"No fix has been published for CVE-2025-8134 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-8134 is a medium-severity SQL injection vulnerability in PHPGurukul BP Monitoring Management System, published on 25 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-8134 and fix it if it is affected.\n\nWhat it is: CVE-2025-8134 is a medium-severity SQL injection vulnerability in PHPGurukul BP Monitoring Management System, published on 25 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8134 exists.\n\nAffected product: PHPGurukul BP Monitoring Management System. 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-8134/ (Markdown: https://insights.sbomify.com/CVE-2025-8134/index.md)","id":"CVE-2025-8134","markdown":"https://insights.sbomify.com/CVE-2025-8134/index.md","name":"CVE-2025-8134","record":{"aliases":["GHSA-w466-769j-w8jf"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"BP Monitoring Management System","requires_auth":"low_privilege","summary":"Remote attackers can exploit SQL injection in the date report feature to read or modify database contents.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"bp_monitoring_management_system","vendor":"phpgurukul"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"},{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"A vulnerability classified as critical was found in PHPGurukul BP Monitoring Management System 1.0. This vulnerability affects unknown code of the file /bwdates-report-result.php. The manipulation of the argument fromdate/todate leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.","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":"PHPGurukul BP Monitoring Management System bwdates-report-result.php sql injection","id":"CVE-2025-8134","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2025"},"n_packages":0,"n_references":7,"next":{"headline":"itsourcecode Insurance Management System updateAgent.php sql injection","id":"CVE-2025-8135"},"packages":[],"prev":{"headline":"yanyutao0402 ChanCMS gather.js getArticle server-side request forgery","id":"CVE-2025-8133"},"products":["BP Monitoring Management System"],"published":"2025-07-25","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2023-27074","kev_date_added":null,"published":"2023-03-14"},{"cvss_score":6.9,"headline":"PHPGurukul BP Monitoring Management System registration.php sql injection","id":"CVE-2025-5856","kev_date_added":null,"published":"2025-06-09"},{"cvss_score":6.3,"headline":"PHPGurukul BP Monitoring Management System Change Password change-password.php sql injection","id":"CVE-2023-1949","kev_date_added":null,"published":"2023-04-08"},{"cvss_score":6.3,"headline":"PHPGurukul BP Monitoring Management System Password Recovery password-recovery.php sql injection","id":"CVE-2023-1950","kev_date_added":null,"published":"2023-04-08"},{"cvss_score":5.3,"headline":"PHPGurukul BP Monitoring Management System edit-family-member.php sql injection","id":"CVE-2025-5761","kev_date_added":null,"published":"2025-06-06"},{"cvss_score":4.7,"headline":"PHPGurukul BP Monitoring Management System User Profile Update profile.php sql injection","id":"CVE-2023-1909","kev_date_added":null,"published":"2023-04-07"}],"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":"partial"},"state":"PUBLISHED","updated":"2025-07-25","vendors":["PHPGurukul"]},"summary":"Remote attackers can exploit SQL injection in the date report feature to read or modify database contents.","url":"https://insights.sbomify.com/CVE-2025-8134/"}