CVE-2026-6167
SQL Injection in Faculty Management System /subject-print.php Allows Remote Exploitation
Publication date: 2026-04-13
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 |
|---|---|---|
| code-projects | faculty_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. |
| 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?
This vulnerability is a SQL injection flaw found in the Faculty Management System version 1.0, specifically in the file /subject-print.php. It occurs because the application improperly handles the 'id' parameter, using it directly in SQL queries without proper input validation or sanitization.
Attackers can exploit this by injecting malicious SQL code through the 'id' parameter, which allows them to manipulate database queries in unauthorized ways. This can be done remotely and does not require any user authentication.
Technical exploitation methods include Boolean-based blind SQL injection, time-based blind SQL injection, and UNION-based SQL injection, enabling attackers to extract or alter data, or even gain full control over the system.
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, data leakage, and data tampering. Attackers may gain full system control and potentially disrupt services, severely compromising system security and business continuity.
- Unauthorized access to sensitive data stored in the database.
- Modification or deletion of critical data.
- Complete takeover of the affected system.
- Potential service disruption affecting availability.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability in the Faculty Management System 1.0 can be detected by testing the `id` parameter in the `/subject-print.php` file for injection flaws.
- Use Boolean-based blind SQL injection payloads such as: `id=4' AND 5584=5584 AND 'qMna'='qMna`.
- Use Time-based blind SQL injection payloads like: `id=4' AND (SELECT 3126 FROM (SELECT(SLEEP(5)))WHqZ) AND 'DusQ'='DusQ`.
- Use UNION-based SQL injection payloads exploiting seven columns, for example: `id=4' UNION ALL SELECT NULL,NULL,NULL,NULL,NULL,CONCAT(0x716b707171,0x48767471724f4846446d764578424c6b54427953724b45734743754f6a6a456f5a675543627072,0x716a706b71),NULL-- -`.
Automated tools like sqlmap can be used to confirm the vulnerability and enumerate the database.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps for this SQL injection vulnerability include:
- Implement prepared statements with parameter binding to separate SQL code from user input, preventing injection.
- Enforce strict input validation and filtering to ensure inputs conform to expected formats.
- Minimize database user permissions by avoiding the use of high-privilege accounts (such as root or admin) for routine database operations.
- Conduct regular security audits to detect and address vulnerabilities promptly.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in the Faculty Management System 1.0 allows attackers to perform unauthorized database access, data leakage, and data tampering without authentication. Such unauthorized access and potential exposure of sensitive data can lead to non-compliance with common standards and regulations like GDPR and HIPAA, which mandate the protection of personal and sensitive information.
Failure to prevent such vulnerabilities may result in breaches of confidentiality, integrity, and availability of data, which are core requirements under these regulations. This can lead to legal penalties, reputational damage, and loss of trust.