CVE-2025-7559
BaseFortify
Publication date: 2025-07-14
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 | online_fire_reporting_system | 1.2 |
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-7559 is a critical SQL injection vulnerability in PHPGurukul Online Fire Reporting System version 1.2. It occurs in the file /admin/bwdates-report-result.php due to improper handling of the fromdate and todate parameters, which are incorporated into SQL queries without proper sanitization or validation. This allows attackers to inject malicious SQL code remotely, potentially manipulating database queries and executing arbitrary database operations. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to unauthorized database access, data leakage, data manipulation, full system compromise, and potential service disruption. Attackers can execute various SQL injection techniques to extract or alter sensitive data, disrupt system operations, and compromise the integrity and availability of the affected system. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the vulnerable parameter "todate" in the /admin/bwdates-report-result.php file for SQL injection. You can use tools like sqlmap to automate detection. Example command: sqlmap -u "http://target/admin/bwdates-report-result.php" --data="todate=2025-08-01" --risk=3 --level=5 --batch. Additionally, manual testing can be done using payloads such as: todate=2025-08-01' AND 4644=4644-- to check for boolean-based blind SQL injection, or time-based payloads like todate=2025-08-01' AND SLEEP(5)-- to detect time delays indicating injection. Also, Google dorking with the query inurl:admin/bwdates-report-result.php can help identify vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the fromdate and todate parameters to ensure they conform to expected date formats, and restricting database user permissions to the minimum necessary to reduce impact if exploited. If possible, replace the affected software with an alternative product. These measures help protect data integrity and system security. [2, 3]