CVE-2025-8157
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-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-8157 is a SQL Injection vulnerability in the PHPGurukul User Registration & Login and User Management System version 3.3. It occurs in the admin panel file lastthirtyays-reg-users.php where the 'id' parameter is not properly sanitized or validated before being used in an SQL query. This allows an attacker, potentially with admin authentication, to inject malicious SQL code remotely, using techniques such as time-based blind SQL injection, to manipulate the database queries executed by the application. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to bypass input filters and execute arbitrary SQL commands on your database. This can lead to unauthorized access to sensitive information such as user data (emails, phone numbers), dumping of the entire database schema, and potentially modifying or deleting data. It compromises the confidentiality, integrity, and availability of your system. The vulnerability can be exploited remotely and easily, increasing the risk of data breaches and system compromise. [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 admin panel file `/admin/lastthirtyays-reg-users.php` for SQL injection on the `id` parameter. A proof of concept involves sending a GET request with an `id` parameter, for example: `/loginsystem/admin/lastthirtyays-reg-users.php?id=1` with a valid admin session cookie. Tools like sqlmap can be used to automate detection with high risk and level settings to enumerate databases. Additionally, vulnerable targets can be identified using Google dorking with the query `inurl:admin/lastthirtyays-reg-users.php`. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing vulnerable SQL queries with parameterized prepared statements to prevent SQL injection, for example: ``` $stmt = $con->prepare("DELETE FROM users WHERE id = ?"); $stmt->bind_param("i", $adminid); $stmt->execute(); ``` Additionally, validate and sanitize all user inputs, especially GET and POST parameters. Enable a Web Application Firewall (WAF) to block malicious requests, monitor admin activity logs for suspicious behavior, and apply least privilege principles to database user accounts. If possible, replace the affected product with an alternative solution as no known countermeasures have been reported. [2, 3]