CVE-2025-8134
BaseFortify
Publication date: 2025-07-25
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| phpgurukul | bp_monitoring_management_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-8134 is a SQL Injection vulnerability in PHPGurukul BP Monitoring Management System version 1.0, specifically in the file /bwdates-report-result.php. The vulnerability arises because the 'fromdate' and 'todate' parameters are not properly sanitized or escaped before being used in SQL queries. This allows an attacker to inject arbitrary SQL code remotely without authentication, potentially manipulating the database queries to access, modify, or delete data. [1, 2, 3, 4]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized access to the database, allowing attackers to extract sensitive information, tamper with or delete data, and potentially cause denial of service by manipulating database operations. It can result in full compromise of the underlying database and the system relying on it, impacting confidentiality, integrity, and availability. [1, 2, 4]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'fromdate' and 'todate' parameters in the /bwdates-report-result.php file for SQL injection flaws. One approach is to use automated tools like sqlmap to send crafted POST requests to the endpoint, for example: sqlmap -u "http://target/bpmms/bwdates-report-result.php" --data="fromdate=1111-11-11&todate=2025-01-01" --risk=3 --level=5 --batch. Additionally, Google dorking with queries such as 'inurl:bwdates-report-result.php' can help identify vulnerable targets. Monitoring for unusual database errors or unexpected behavior in logs when these parameters are used may also indicate exploitation attempts. [2, 4]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replacing the affected software with an alternative product if possible. 2) Applying input validation and sanitization to the 'fromdate' and 'todate' parameters to prevent SQL injection. 3) Refactoring the code to use prepared statements with PDO or MySQLi to parameterize SQL queries. 4) Limiting database user privileges to avoid using high-privilege accounts such as root. 5) Deploying a Web Application Firewall (WAF) to detect and block SQL injection attempts. 6) Conducting regular security audits and code reviews to identify and fix vulnerabilities. [2, 4]