CVE-2025-7560
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-7560 is a critical SQL injection vulnerability in the PHPGurukul Online Fire Reporting System version 1.2. It exists in the /admin/workin-progress-requests.php file, specifically involving the 'teamid' parameter. This parameter is used directly in SQL queries without proper sanitization or validation, allowing attackers to inject malicious SQL code remotely. Exploiting this flaw enables attackers to manipulate SQL queries and perform unauthorized database operations. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data manipulation, and potentially full system compromise. Attackers can execute arbitrary SQL commands remotely without authentication, which may severely impact system security and business continuity by compromising the confidentiality, 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 'teamid' parameter in the /admin/workin-progress-requests.php file for SQL injection. A common method is using time-based blind SQL injection payloads such as: teamid=1' RLIKE SLEEP(5)-- tbzp to observe delayed responses indicating injection. Tools like sqlmap can be used with parameters targeting the 'teamid' parameter to automate detection and enumeration of databases. Additionally, Google dorking with queries like inurl:admin/workin-progress-requests.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 separate SQL code from user input, enforcing rigorous input validation and filtering on the 'teamid' parameter to ensure it conforms to expected formats, and minimizing database user permissions by avoiding elevated privilege accounts for routine operations. If possible, replacing the affected software with an alternative product is recommended as no known mitigations are documented. [2, 3]