CVE-2025-69991
BaseFortify
Publication date: 2026-01-13
Last updated on: 2026-01-16
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| phpgurukul | news_portal | 4.1 |
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?
The vulnerability in phpgurukul News Portal Project V4.1 is an SQL Injection found in the check_availablity.php file. This means that an attacker can manipulate the SQL queries executed by this script, potentially allowing unauthorized access or manipulation of the database. [1]
How can this vulnerability impact me? :
This SQL Injection vulnerability can allow attackers to access, modify, or delete sensitive data stored in the database. It may lead to data breaches, loss of data integrity, unauthorized data disclosure, or even full system compromise depending on the database privileges. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the check_availablity.php script for SQL Injection vulnerabilities. You can use SQL injection testing tools or manual commands such as sending crafted HTTP requests with SQL payloads to the check_availablity.php endpoint and observing the responses for SQL errors or unexpected behavior. For example, using curl: curl -X GET "http://yourserver/check_availablity.php?param=' OR '1'='1" to check if the input is vulnerable to SQL injection. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include validating and sanitizing all user inputs in check_availablity.php, using prepared statements or parameterized queries to prevent SQL injection, and applying any available patches or updates to the News Portal Project. Additionally, restricting database permissions and monitoring logs for suspicious activity can help reduce risk. [1]