CVE-2026-26698
SQL Injection in code-projects Simple Student Alumni System
Publication date: 2026-03-02
Last updated on: 2026-03-03
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 v1.0 is an SQL Injection found in the /TracerStudy/modal_edit.php file.
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 /TracerStudy/modal_edit.php of the code-projects Simple Student Alumni System v1.0. Detection can involve testing this specific endpoint for SQL Injection flaws.'}, {'type': 'list_item', 'content': 'Use tools like sqlmap to test the URL: sqlmap -u "http://target/TracerStudy/modal_edit.php" --data="id=1" --batch'}, {'type': 'list_item', 'content': "Manually test by injecting SQL payloads in the 'id' parameter of /TracerStudy/modal_edit.php, such as adding ' OR '1'='1 to see if the response changes."}, {'type': 'list_item', 'content': 'Monitor web server logs for suspicious requests targeting /TracerStudy/modal_edit.php with SQL keywords or unusual characters.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include sanitizing and validating all user inputs on /TracerStudy/modal_edit.php to prevent SQL Injection.
- Implement prepared statements or parameterized queries in the backend code handling the modal_edit.php requests.
- Apply web application firewall (WAF) rules to block common SQL Injection attack patterns targeting this endpoint.
- Restrict database user permissions to limit the impact of a potential SQL Injection.
- If possible, update or patch the Simple Student Alumni System to a version that fixes this vulnerability.