CVE-2026-9575
SQL Injection in Student Transcript Processing System
Publication date: 2026-05-26
Last updated on: 2026-05-26
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| itsourcecode | student_transcript_processing_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?
The CVE-2026-9575 vulnerability is a SQL injection flaw found in the Student Transcript Processing System 1.0, specifically in the file /admin/modules/class/index.php?view=view. It occurs due to insufficient input validation of the 'id' parameter, which allows attackers to inject malicious SQL queries.
This vulnerability can be exploited remotely without requiring login or authorization, using techniques such as time-based blind or UNION query injections.
Successful exploitation can lead to unauthorized database access, data tampering, leakage of sensitive information, and potentially full control over the system.
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to the database, which may result in exposure of sensitive student transcript data.
Attackers could tamper with data, leading to data integrity issues, or gain full control over the system, compromising overall system security.
Because the exploit can be performed remotely without authentication, it increases the risk of widespread attacks.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
The CVE-2026-9575 vulnerability can be detected by testing the 'id' parameter in the URL /admin/modules/class/index.php?view=view for SQL injection flaws. Tools like sqlmap can be used to automate this detection using time-based blind or UNION query techniques.
- Use sqlmap with a command such as: sqlmap -u "http://target/admin/modules/class/index.php?view=view&id=1" --batch --dbs
- Manually test by injecting SQL payloads into the 'id' parameter, for example: http://target/admin/modules/class/index.php?view=view&id=1' OR '1'='1
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, applying strict input validation on the 'id' parameter, minimizing database user permissions to limit potential damage, and conducting regular security audits to detect and fix vulnerabilities.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL injection vulnerability in the Student Transcript Processing System allows unauthorized database access, data tampering, and sensitive information leakage. Such unauthorized access and potential exposure of sensitive personal data can lead to non-compliance with data protection regulations like GDPR and HIPAA, which mandate the protection of personal and sensitive information.
Failure to secure the system against this vulnerability could result in breaches of confidentiality, integrity, and availability of data, which are core requirements of these standards. This may lead to legal penalties, loss of trust, and other compliance-related consequences.