CVE-2026-9573
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
How can this vulnerability impact me? :
Exploitation of this vulnerability can have severe impacts including unauthorized access to sensitive student data, leakage of confidential information, alteration or tampering of database records, gaining control over the system, and disruption of service availability.
Since the attack can be performed remotely without authentication, it poses a significant security risk to the affected system and its users.
Can you explain this vulnerability to me?
CVE-2026-9573 is a SQL injection vulnerability found in the Student Transcript Processing System version 1.0. It occurs in the file /admin/modules/student/index.php?view=view, specifically through manipulation of the studentId parameter. Due to insufficient input validation, an attacker can inject malicious SQL queries remotely without needing authentication.
This flaw allows attackers to execute unauthorized database commands, potentially leading to unauthorized access, data leakage, data tampering, system control, and service disruption.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
The CVE-2026-9573 vulnerability can be detected by testing the `studentId` parameter in the URL `/admin/modules/student/index.php?view=view&studentId=1` for SQL injection flaws.
Tools like sqlmap can be used to identify this vulnerability by automating SQL injection detection.
- Use sqlmap with a command such as: sqlmap -u "http://target/admin/modules/student/index.php?view=view&studentId=1" --batch
- Manually test by injecting SQL payloads into the studentId parameter, such as adding `' OR '1'='1` or time-based blind SQL injection payloads.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection.
Strict input validation should be applied to the studentId parameter to ensure only valid input is accepted.
Minimize database user permissions to limit the impact of any potential exploitation.
Conduct regular security audits to detect and address vulnerabilities proactively.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The CVE-2026-9573 vulnerability allows remote SQL injection attacks that can lead to unauthorized database access, data leakage, and tampering. Such unauthorized access and potential exposure of sensitive student data could result in non-compliance with data protection regulations like GDPR and HIPAA, which mandate strict controls over personal and health-related information to ensure confidentiality, integrity, and availability.
Failure to address this vulnerability may expose organizations to regulatory penalties and legal consequences due to breaches of protected data, as well as damage to reputation and trust.