Live Active security incident? Get immediate response
CVE Record

CVE-2026-9469: yashpokharna2555 StudentManagementSystem success.php sql injection

A weakness has been identified in yashpokharna2555 StudentManagementSystem cb2f558ddf8d19396de0f92abf2d224d46a0a203. The impacted element is an unknown function of the file /success.php. This manipulation of the argument User causes sql injection. It is possible to initiate the attack remotely. The exploit has been made available to the public and could be used for attacks. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available. The project was informed of the problem early through an issue report but has not responded yet.

HighCVSS 7.5Not KEV-listed Updated
Discuss exposure Back to CVEs
Glexia's Take high

Analyst readout for executives and security teams

Plain-English summary

CVE-2026-9469 affects a GitHub StudentManagementSystem project. A remote, unauthenticated attacker may be able to manipulate database queries through the User argument in /success.php, risking student-system data exposure, alteration, or disruption. The sources do not identify a fixed version or vendor response.

Executive priority

Treat as high priority if this project is deployed in production or exposed to the internet. The combination of remote unauthenticated reachability, database impact, public exploit availability, and no identified fix increases operational urgency.

Technical view

The reported flaw is SQL injection in /success.php via the User argument in yashpokharna2555 StudentManagementSystem commit cb2f558ddf8d19396de0f92abf2d224d46a0a203. It is mapped to CWE-89 and CWE-74, scored CVSS v2 7.5, and described as remotely exploitable without authentication. Rolling-release versioning leaves affected and fixed release boundaries unclear.

Likely exposure

Exposure is likely limited to organizations running this specific open-source StudentManagementSystem code or derivatives, especially if /success.php is internet-accessible. The source bundle provides no evidence of broad commercial distribution or deployment prevalence.

Exploitation context

The CVE and VulDB entry state that a public exploit exists and remote attack is possible. KEV is false, and the provided sources do not confirm active exploitation in the wild.

Researcher notes

Evidence is mainly from CVE/VulDB records and a GitHub issue. The affected function is not named, version boundaries are unclear because of rolling release delivery, and no active exploitation evidence is provided. Avoid assuming all student management systems are affected.

Mitigation direction

  • Inventory any StudentManagementSystem deployments and forks using the affected commit lineage.
  • Restrict public access to /success.php until the application is reviewed or fixed.
  • Check the upstream repository and issue tracker for vendor guidance before restoring exposure.
  • Apply SQL parameterization and input validation if maintaining a private fork.
  • Monitor application logs for unusual requests involving the User argument.

Validation and detection

  • Confirm whether any deployed code includes /success.php from the affected project.
  • Review /success.php database handling for unparameterized use of the User argument.
  • Check web access logs for unexpected or high-volume requests to /success.php.
  • Verify whether the upstream repository has acknowledged or remediated issue 2.
  • Assess whether compensating controls block unauthenticated access to the affected route.
Prepared
Confidence
medium
Sources
7

Public sources used

Based on public source material and reviewed before publication.

Potential ATT&CK relevance

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 · low confidence lookup

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 lookup
cwe · medium confidence lookup

CWE-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 lookup
description · low confidence lookup

Database 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 lookup
cve · low confidence lookup

CVE-2026-9469 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profile CVE Program record
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

Official CVE source material

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.

4 CVSS vectors
6 Timeline events
1 ADP providers
6 Source links

SSVC decision data

CISA-ADP CISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: partial

CVSS vector scores

4 official scores

We 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.

Score Version Severity Vector Exploit Impact Source
7.5 CVSS 2.0 High AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:ND/RC:UR 10 6.4 VulDB
7.3 CVSS 3.1 High 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
7.3 CVSS 3.0 High 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
6.9 CVSS 4.0 Medium 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 Medium
CVSS 4.0 vector shape for CVE-2026-9469 Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timeline VulDB

    Advisory disclosed

  2. Source timeline VulDB

    VulDB entry created

  3. CVE reserved CVE Program

    The CVE ID was reserved by the assigning CNA.

  4. Source timeline VulDB

    VulDB entry last update

  5. CVE published CVE Program

    The CVE record was published.

  6. CVE updated CVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADP CISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

Vendor Product Version / package Status
yashpokharna2555 StudentManagementSystem cb2f558ddf8d19396de0f92abf2d224d46a0a203 Listed
Weakness

CWE details

CWE-74CWE-89

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-74 · source CWE mapping

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.

Open CWE intelligence Same-CWE CVEs
CWE-89 · source CWE mapping

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.

Open CWE intelligence Same-CWE CVEs