Analyst readout for executives and security teams
Plain-English summary
CVE-2026-9575 is a SQL injection issue in itsourcecode Student Transcript Processing System 1.0. A remote unauthenticated attacker may be able to affect database confidentiality, integrity, and availability through the ID parameter on an admin class view page. Public exploit information is referenced, but the bundle does not show confirmed active exploitation.
Executive priority
Treat this as a high-priority exposure review if the product is deployed. Public disclosure increases practical risk, but urgency depends on whether the application is reachable from untrusted users and whether sensitive transcript data is stored behind it.
Technical view
The reported flaw affects /admin/modules/class/index.php?view=view, where manipulation of the ID argument leads to SQL injection. The CVSS v2 score is 7.5 with network access, low complexity, and no authentication. The CVE maps to CWE-89 and CWE-74. No official patch or vendor mitigation is named in the provided sources.
Likely exposure
Exposure appears limited to organizations running itsourcecode Student Transcript Processing System 1.0, especially if the admin modules are reachable from untrusted networks. The source bundle does not identify other affected versions or products.
Exploitation context
The sources state that exploit details have been publicly disclosed and may be used. The CVE is not listed as KEV in the provided bundle, and no cited source confirms active exploitation in the wild.
Researcher notes
Evidence is sufficient for a high-risk SQL injection classification, but operational details are thin. The bundle does not provide a vendor fix, affected code confirmation beyond the endpoint and parameter, or evidence of active exploitation. Avoid expanding affected scope beyond version 1.0.
Mitigation direction
- Identify any deployments of Student Transcript Processing System 1.0.
- Restrict access to the affected admin path from untrusted networks.
- Check itsourcecode and VulDB for vendor guidance or patch information.
- Monitor web logs for unusual ID parameter activity on the affected path.
- If maintaining code locally, review database handling around the ID parameter.
Validation and detection
- Confirm whether version 1.0 is deployed in production or exposed environments.
- Verify whether /admin/modules/class/index.php?view=view is externally reachable.
- Review recent access logs for suspicious requests targeting the ID parameter.
- Check whether compensating controls block unexpected requests to admin modules.
- Track the CVE and vendor references for patch or mitigation updates.
Public sources used
Based on public source material and reviewed before publication.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-74: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-9575 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (2.0)
- Known Exploited
- No
- Published
Vector: AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
4 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR 10 6.4 VulDB CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R 3.9 3.4 VulDB CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R 3.9 3.4 VulDB CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P — — VulDB Vulnerability scoring details
Base CVSS 4.0 score
6.9 MediumVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
Base CVSS 3.1 score
7.3 HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R
Base CVSS 3.0 score
7.3 HighVector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R
Base CVSS 2.0 score
7.5 HighVector: AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timeline VulDB
Advisory disclosed
- Source timeline VulDB
VulDB entry created
- CVE reserved CVE Program
The CVE ID was reserved by the assigning CNA.
- Source timeline VulDB
VulDB entry last update
- CVE published CVE Program
The CVE record was published.
- CVE updated CVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 source CVE List V5
- VDB-365634 | itsourcecode Student Transcript Processing System index.php sql injection CVE reference, VulDB · vdb-entry, technical-description
- VDB-365634 | CTI Indicators (IOB, IOC, TTP, IOA) CVE reference, VulDB · signature, permissions-required
- Submit #817580 | itsourcecode Student Transcript Processing System V1.0 SQL Injection CVE reference, VulDB · third-party-advisory
- https://github.com/nidieaaa/test/issues/14 CVE reference, VulDB · exploit, issue-tracking
- https://itsourcecode.com/ CVE reference, VulDB · product
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.