Security readout for executives and security teams
Plain-English summary
CVE-2026-1176 is a SQL injection issue in itsourcecode School Management System 1.0. A remote unauthenticated attacker may manipulate the ID parameter in /subject/index.php to affect the database. Public exploit information exists, but the provided sources do not show confirmed active exploitation or CISA KEV listing.
Executive priority
Treat as a high-priority application risk if this system is deployed, especially if internet-facing. The combination of remote unauthenticated access, database impact, and public exploit availability warrants rapid inventory, exposure reduction, and vendor-guidance review.
Technical view
The issue affects an unspecified function in /subject/index.php. Manipulation of the ID argument can cause SQL injection, mapped to CWE-89 and CWE-74. The CVSS v2 score is 7.5 with network access, low complexity, and no authentication required. VulDB reports proof-of-concept exploit availability.
Likely exposure
Exposure is most likely where itsourcecode School Management System 1.0 is internet-facing or reachable by untrusted users. Risk increases if the application stores sensitive student, staff, or administrative data in the connected database.
Exploitation context
The sources state the attack can be initiated remotely and that public exploit material exists. They do not provide evidence of active exploitation in the wild. No KEV listing is indicated in the provided bundle.
Researcher notes
Evidence comes primarily from VulDB and the CVE record. The affected version is listed as 1.0, but the CPE wildcard in the bundle is broader; validate actual installed code before scoping. No source in the bundle names a fixed version or official patch.
Mitigation direction
- Identify whether School Management System 1.0 is deployed and reachable.
- Check itsourcecode and VulDB references for vendor guidance or updates.
- Restrict access to the application from untrusted networks where possible.
- Apply web application firewall rules for suspicious requests to /subject/index.php.
- Ensure database accounts used by the app have least privilege.
- If maintaining code, use parameterized queries for ID handling.
Validation and detection
- Inventory deployed school management applications and confirm product/version.
- Check whether /subject/index.php is accessible externally or to untrusted users.
- Review web logs for unusual ID parameter activity on /subject/index.php.
- Review database logs for suspicious queries tied to that endpoint.
- Confirm whether vendor patches, updates, or advisories have been applied.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-1176 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.
CVSS vector scores
1 official scoreWe 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:UR106.4Primary CVE scoreVulnerability scoring details
Base CVSS 2.0 score
7.5HighVector: AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
Source materials
- CVE List V5 sourceCVE List V5
- VDB-341770 | itsourcecode School Management System index.php sql injectionCVE reference · vdb-entry, technical-description
- VDB-341770 | CTI Indicators (IOB, IOC, TTP, IOA)CVE reference · signature, permissions-required
- Submit #736477 | itsourcecode School Management System V1.0 SQL InjectionCVE reference · third-party-advisory
- https://github.com/ltranquility/CVE/issues/32CVE reference · exploit, issue-tracking
- https://itsourcecode.com/CVE reference · 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.