CVE-2026-26695
SQL Injection in code-projects Alumni System Allows Data Manipulation
Publication date: 2026-03-02
Last updated on: 2026-03-05
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| carmelo | simple_student_alumni_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?
The vulnerability in code-projects Simple Student Alumni System version 1.0 is an SQL Injection found in the file /TracerStudy/recordstudent_edit.php.
How can this vulnerability impact me? :
An SQL Injection vulnerability can allow an attacker to manipulate the database queries executed by the application. This can lead to unauthorized access to sensitive data, data modification, or even deletion of data within the system.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'The vulnerability is an SQL Injection in the /TracerStudy/recordstudent_edit.php file of the code-projects Simple Student Alumni System v1.0. Detection typically involves testing this endpoint for SQL Injection flaws.'}, {'type': 'paragraph', 'content': 'Common commands to detect SQL Injection include using tools like sqlmap or manual testing with payloads in HTTP requests targeting the vulnerable parameter in /TracerStudy/recordstudent_edit.php.'}, {'type': 'list_item', 'content': 'Use sqlmap with a command such as: sqlmap -u "http://target/TracerStudy/recordstudent_edit.php?param=value" --batch'}, {'type': 'list_item', 'content': "Manually test by injecting SQL payloads in the URL or POST parameters, for example: ' OR '1'='1"}] [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include validating and sanitizing all user inputs on the /TracerStudy/recordstudent_edit.php page to prevent SQL Injection.
Use prepared statements or parameterized queries in the code to avoid direct concatenation of user inputs into SQL queries.
If possible, apply any available patches or updates from the vendor or source code repository.
Restrict database permissions to limit the impact of a potential SQL Injection attack.