CVE-2025-70892
BaseFortify
Publication date: 2026-01-15
Last updated on: 2026-01-15
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| phpgurukul | cyber_cafe_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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a SQL Injection in the Phpgurukul Cyber Cafe Management System v1.0. It occurs because the application does not properly validate user input in the username parameter of the add-users.php endpoint. This allows an attacker to inject malicious SQL code, potentially manipulating the database. [2]
How can this vulnerability impact me? :
The SQL Injection vulnerability can lead to severe impacts including unauthorized access to sensitive data, modification or deletion of database records, and full compromise of the system's confidentiality, integrity, and availability. Given the CVSS score of 9.8, it is highly critical and can allow attackers to control the system remotely without any privileges or user interaction. [2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect this SQL Injection vulnerability by testing the 'username' parameter in the add-users.php endpoint for improper input validation. For example, you can use tools like sqlmap or manual curl commands to inject SQL payloads and observe the response. A sample curl command to test might be: curl -X POST -d "username=' OR '1'='1" http://<target>/add-users.php. Monitoring web server logs for suspicious input patterns in the username parameter can also help detect exploitation attempts. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying proper input validation and sanitization on the 'username' parameter in add-users.php to prevent SQL Injection. Use prepared statements or parameterized queries in the PHP code when interacting with the database. Additionally, restrict database user permissions to the minimum necessary and monitor logs for suspicious activity. If a patch or updated version is available from the vendor or source, apply it promptly. [1]