{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5612 exists.","fix":"No fix has been published for CVE-2025-5612 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-5612 is a medium-severity SQL injection vulnerability in PHPGurukul Online Fire Reporting System, published on 4 Jun 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-5612 and fix it if it is affected.\n\nWhat it is: CVE-2025-5612 is a medium-severity SQL injection vulnerability in PHPGurukul Online Fire Reporting System, published on 4 Jun 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-5612 exists.\n\nAffected product: PHPGurukul Online Fire Reporting 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-5612/ (Markdown: https://insights.sbomify.com/CVE-2025-5612/index.md)","id":"CVE-2025-5612","markdown":"https://insights.sbomify.com/CVE-2025-5612/index.md","name":"CVE-2025-5612","record":{"aliases":["GHSA-4ggm-6pw7-9w49"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Online Fire Reporting System","requires_auth":"low_privilege","summary":"Remote attackers can exploit SQL injection in the reporting.php file to read or modify database contents in the Online Fire Reporting System.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"online_fire_reporting_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","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 has been found in PHPGurukul Online Fire Reporting System 1.2 and classified as critical. This vulnerability affects unknown code of the file /reporting.php. The manipulation of the argument fullname leads to sql injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. Other parameters might be affected as well.","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 Online Fire Reporting System reporting.php sql injection","id":"CVE-2025-5612","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"PHPGurukul Online Fire Reporting System request-details.php sql injection","id":"CVE-2025-5613"},"packages":[],"prev":{"headline":"CodeAstro Real Estate Management System submitpropertyupdate.php sql injection","id":"CVE-2025-5611"},"products":["Online Fire Reporting System"],"published":"2025-06-04","related":[{"cvss_score":9.3,"headline":"SQL injection in PHPGurukul Online Fire Reporting System","id":"CVE-2025-40687","kev_date_added":null,"published":"2025-09-11"},{"cvss_score":9.3,"headline":"SQL injection in PHPGurukul Online Fire Reporting System","id":"CVE-2025-40689","kev_date_added":null,"published":"2025-09-11"},{"cvss_score":9.3,"headline":"SQL injection in PHPGurukul Online Fire Reporting System","id":"CVE-2025-40690","kev_date_added":null,"published":"2025-09-11"},{"cvss_score":9.3,"headline":"SQL injection in PHPGurukul Online Fire Reporting System","id":"CVE-2025-40691","kev_date_added":null,"published":"2025-09-11"},{"cvss_score":9.3,"headline":"SQL injection in PHPGurukul Online Fire Reporting System","id":"CVE-2025-40692","kev_date_added":null,"published":"2025-09-11"},{"cvss_score":9.1,"headline":"SQL injection in n/a","id":"CVE-2024-34987","kev_date_added":null,"published":"2024-06-03"},{"cvss_score":6.9,"headline":"PHPGurukul Online Fire Reporting System search-request.php sql injection","id":"CVE-2025-3238","kev_date_added":null,"published":"2025-04-04"}],"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-06-05","vendors":["PHPGurukul"]},"summary":"Remote attackers can exploit SQL injection in the reporting.php file to read or modify database contents in the Online Fire Reporting System.","url":"https://insights.sbomify.com/CVE-2025-5612/"}