CVE-2025-8158
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 | user_registration_\&_login_and_user_management_system | 3.3 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-8158 is a critical SQL injection vulnerability in PHPGurukul Login and User Management System version 3.3, specifically in the file /admin/yesterday-reg-users.php. The vulnerability occurs because the application improperly handles the 'id' parameter from a GET request, directly inserting it into an SQL query without validation or using prepared statements. This allows an attacker to manipulate the SQL query, potentially executing arbitrary SQL commands on the database. The flaw affects the confidentiality, integrity, and availability of the system and can be exploited remotely, sometimes requiring admin authentication depending on the context. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized access and manipulation of the database. An attacker can read sensitive information such as user emails and phone numbers, dump the entire database, modify or delete data, and potentially escalate privileges by chaining with other vulnerabilities. The system's confidentiality, integrity, and availability are at risk. Exploitation can be done remotely and may be automated using tools like sqlmap, making it easy for attackers to compromise 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 identifying access to the vulnerable endpoint `/admin/yesterday-reg-users.php` with suspicious or malicious `id` parameter values that may indicate SQL injection attempts. One method is to use Google dorking with the query `inurl:admin/yesterday-reg-users.php` to find potentially vulnerable targets. Additionally, automated tools like sqlmap can be used to test the endpoint for SQL injection by sending crafted GET requests, for example: `sqlmap -u "http://target/loginsystem/admin/yesterday-reg-users.php?id=1" --cookie="admin_session=your_session_cookie"`. Monitoring web server logs for unusual requests to this URL with SQL injection payloads is also recommended. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the vulnerable SQL query with parameterized prepared statements to prevent SQL injection, for example using prepared statements in PHP: `$stmt = $con->prepare("DELETE FROM users WHERE id = ?"); $stmt->bind_param("i", $adminid); $stmt->execute();`. Additionally, validate and sanitize all user inputs, especially GET parameters like `id`. Enabling a Web Application Firewall (WAF) to block malicious requests, monitoring admin activity logs for anomalies, and applying least privilege principles to database user accounts are also recommended. If possible, replace the affected component with an alternative product. [1, 3]