CVE-2026-5838
SQL Injection in PHPGurukul News Portal /admin/add-subadmins.php
Publication date: 2026-04-09
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 | news_portal_project | 4.1 |
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?
The vulnerability exists in the PHPGurukul News Portal Project version 4.1, specifically in the file "/admin/add-subadmins.php" within the "sadminusername" POST parameter.
This vulnerability is a SQL injection caused by the direct incorporation of user input from "sadminusername" into SQL queries without proper sanitization or validation.
Attackers can exploit this flaw by injecting malicious SQL code remotely, which can manipulate the database queries executed by the application.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in PHPGurukul News Portal Project 4.1 allows unauthorized database access, data leakage, and data tampering. Such security weaknesses can lead to breaches of sensitive personal or protected health information, which would negatively impact compliance with standards like GDPR and HIPAA that require protection of data confidentiality, integrity, and availability.
Failure to remediate this vulnerability could result in unauthorized disclosure or alteration of regulated data, potentially causing violations of data protection regulations and leading to legal and financial consequences.
Mitigation steps such as using prepared statements, input validation, and limiting database permissions are critical to maintaining compliance by safeguarding data against injection attacks.
How can this vulnerability impact me? :
Exploitation of this SQL injection vulnerability can lead to unauthorized database access, allowing attackers to view, modify, or delete sensitive data.
Attackers may gain full system control, potentially disrupting services and compromising business continuity.
The vulnerability poses significant risks to system security, including data leakage, data tampering, and service disruption.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the "sadminusername" POST parameter in the file "/admin/add-subadmins.php" for SQL injection flaws.
A common approach is to use automated tools like sqlmap to perform time-based blind SQL injection tests targeting the "sadminusername" parameter.
- Use sqlmap with a command similar to: sqlmap -u "http://target/admin/add-subadmins.php" --data="sadminusername=TEST" --technique=T --dbms=MySQL
- Manually test by submitting crafted inputs to the "sadminusername" parameter and observe if SQL errors or unexpected behavior occur.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include:
- Implement prepared statements with parameter binding to separate SQL code from user input, preventing SQL injection.
- Apply strict input validation and filtering on the "sadminusername" parameter to ensure inputs conform to expected formats and block malicious data.
- Limit database user permissions to the minimum necessary, avoiding the use of high-privilege accounts such as 'root' or 'admin' for routine operations.