CVE-2025-5856
BaseFortify
Publication date: 2025-06-09
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-5856 is a critical SQL injection vulnerability in PHPGurukul BP Monitoring Management System version 1.0, specifically in the /registration.php file. It occurs due to improper validation of the 'emailid' parameter, allowing attackers to inject malicious SQL queries. This enables unauthorized access to the database, potentially leading to data exposure, modification, or deletion. The vulnerability can be exploited remotely without authentication. [1, 2]
How can this vulnerability impact me? :
Exploitation of this vulnerability can compromise the confidentiality, integrity, and availability of the affected system. Attackers can gain unauthorized access to sensitive data, modify or delete information, and disrupt system operations. Since the attack requires no authentication and can be performed remotely, it poses a significant security risk. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by identifying if your system is running PHPGurukul BP Monitoring Management System version 1.0 and if the /registration.php file is accessible. One method to find vulnerable targets is using Google dorking with the query "inurl:registration.php" to locate exposed instances. Additionally, testing the "emailid" parameter in /registration.php for SQL injection by injecting typical SQL payloads (e.g., ' OR '1'='1) can help detect the vulnerability. Network detection might involve monitoring for unusual SQL injection patterns targeting the emailid parameter. Specific commands could include using curl or wget to send crafted requests, for example: curl -G "http://target/registration.php" --data-urlencode "emailid=' OR '1'='1" and observing the response for SQL errors or unexpected behavior. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing or upgrading the affected product or component, as no known mitigations or countermeasures are currently available. It is critical to apply input validation and sanitization on the "emailid" parameter to prevent SQL injection. If possible, restrict access to the /registration.php endpoint and monitor for exploitation attempts. Since the vulnerability is critical and publicly disclosed, consider taking the system offline or isolating it until a secure version or patch is available. [2, 1]