CVE-2025-5761
BaseFortify
Publication date: 2025-06-06
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-5761 is a critical SQL injection vulnerability in PHPGurukul BP Monitoring Management System version 1.0, specifically in the /edit-family-member.php file. The vulnerability occurs because the 'memberage' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This can lead to unauthorized access to the database, enabling attackers to read, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive information, data leakage, data manipulation, and potential full system compromise or service disruption. Attackers can exploit the flaw remotely to execute arbitrary SQL commands, which may result in loss of data integrity, confidentiality, and availability of the system. [1, 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 /edit-family-member.php endpoint for SQL injection via the memberage parameter. A time-based blind SQL injection test can be performed by sending crafted POST requests with payloads that induce delays, such as using the MySQL SLEEP function. For example, using curl to send a POST request with a payload like "memberage=1' OR IF(SLEEP(5),1,0)-- " to observe if the response is delayed, indicating vulnerability. Additionally, vulnerable targets can be identified using Google Dorking with the query: inurl:edit-family-member.php. [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 memberage parameter to ensure it conforms to expected formats, and restricting database user permissions to the minimum necessary to reduce impact. If possible, replacing the affected product with an alternative solution is recommended. These measures help protect system security, maintain data integrity, and ensure operational continuity. [2, 3]