CVE-2025-8156
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-8156 is a critical SQL Injection vulnerability in the PHPGurukul User Registration & Login and User Management System version 3.3. It occurs in the admin panel file `lastsevendays-reg-users.php` where the `id` parameter is not properly sanitized or validated. This allows an attacker, typically with admin session authentication, to inject malicious SQL code via the `id` parameter. The flaw enables time-based blind SQL injection attacks, allowing attackers to bypass input filters and extract sensitive information from the database, such as user emails and phone numbers, or even enumerate the entire database schema. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can impact you by compromising the confidentiality, integrity, and availability of your system. An attacker exploiting this SQL injection flaw can extract sensitive data from your database, modify or delete data, and potentially escalate privileges by chaining this vulnerability with others. The attack can be performed remotely and is considered easy to execute, especially if the attacker has admin session access. This could lead to data breaches, unauthorized data manipulation, and disruption of your user management 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 targeting the vulnerable endpoint `/admin/lastsevendays-reg-users.php` and testing the `id` parameter for SQL injection. One approach is to use sqlmap with an authenticated admin session cookie to test for time-based blind SQL injection. For example, a command might be: `sqlmap -u "http://target/loginsystem/admin/lastsevendays-reg-users.php?id=1" --cookie="admin_session=your_session_cookie" --technique=T --dbs`. Additionally, Google dorking can help identify vulnerable targets using queries like `inurl:admin/lastsevendays-reg-users.php`. [2, 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/POST parameters. Enabling a Web Application Firewall (WAF) to block malicious requests, monitoring admin activity logs for suspicious behavior, and applying least privilege principles to database user accounts are also recommended. If possible, replace the affected component with an alternative product. [3, 2]