CVE-2026-9438: yashpokharna2555 StudentManagementSystem · Improper Control of Resource Identifiers
Affects yashpokharna2555 StudentManagementSystemSource CVE Database V5
Public exploit available · CVSS 5.3 Medium.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 25 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| yashpokharna2555StudentManagementSystem | Affected
| Fixed in– |
CPE configurations (1)
cpe:2.3:a:yashpokharna2555:studentmanagementsystem:*:*:*:*:*:*:*:*
AI-suggested
Since the vendor has not responded or provided a fix, users should monitor for updates from the vendor. In the meantime, restricting access to the affected functionality or implementing input validation controls on the ID parameter may reduce risk.
Description
CVE-2026-9438 is a medium severity vulnerability in the yashpokharna2555 StudentManagementSystem affecting the courseDel.php file. It involves improper control of resource identifiers through manipulation of the ID argument, which can be exploited remotely without user interaction or privileges beyond low. The vulnerability has a CVSS 4.0 base score of 5.3. The product uses a rolling release model, and no specific patch or remediation guidance has been provided by the vendor. The issue was reported early but remains unaddressed, and no known exploits are currently observed in the wild.