CVE-2026-5195
Remote SQL Injection in Student Membership System User Registration
Publication date: 2026-03-31
Last updated on: 2026-03-31
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| code-projects | student_membership_system | 1.0 |
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?
CVE-2026-5195 is a high-severity SQL Injection vulnerability found in the Student Membership System version 1.0, specifically in the user registration feature. The issue occurs because user-supplied data from the $_POST array is directly concatenated into SQL queries without any filtering, escaping, or parameterization.
This insecure coding practice allows an attacker to inject arbitrary SQL commands by crafting malicious input, exploiting the vulnerable code that uses the mysql_query function to insert user data into the database.
As a result, an attacker can manipulate inputs such as firstname, lastname, age, and others to execute arbitrary SQL commands.
How can this vulnerability impact me? :
This vulnerability can have severe impacts including the ability for an attacker to delete database tables, read sensitive data, modify data, or even gain a database shell.
Effectively, this grants the attacker complete control over the database, which can lead to data breaches, loss of data integrity, and disruption of service.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the user registration feature for SQL injection flaws, especially by sending crafted input in the POST data to the /index.php endpoint.
One way to detect it is to manually or automatically inject SQL payloads into the registration form fields (e.g., firstname, lastname) and observe if the application behaves unexpectedly or returns database errors.
For command-line detection, tools like sqlmap can be used to test the endpoint for SQL injection vulnerabilities.
- Example sqlmap command: sqlmap -u "http://targetsite/index.php" --data="firstname=test&lastname=test" --risk=3 --level=5 --batch
- Alternatively, use curl to send crafted POST requests and check for SQL error messages or anomalies in responses.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves fixing the vulnerable code by replacing the direct concatenation of user inputs into SQL queries with prepared statements using PDO or mysqli.
Additionally, enforce strict type validation and proper escaping of all user inputs to prevent injection.
If code changes are not immediately possible, consider applying web application firewall (WAF) rules to block common SQL injection payloads targeting the registration endpoint.
Also, monitor database logs and application logs for suspicious queries or errors that may indicate exploitation attempts.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL Injection vulnerability in the Student Membership System 1.0 allows attackers to read, modify, or delete sensitive data stored in the database. This unauthorized access and manipulation of personal data can lead to violations of data protection regulations such as GDPR and HIPAA, which require the protection of personal and sensitive information from unauthorized access and breaches.
Failure to secure user input and prevent SQL Injection can result in data breaches, exposing personally identifiable information (PII) or protected health information (PHI), thereby compromising compliance with these standards.
Mitigating this vulnerability by implementing prepared statements and input validation is essential to maintain compliance with such regulations.