CVE-2026-9486: SourceCodester Student Grades Management System · Cross-Site Request Forgery
Affects SourceCodester Student Grades Management SystemSource CVE Database V5
Public exploit available · CVSS 5.3 Medium.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/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 |
|---|---|---|
| SourceCodesterStudent Grades Management System | Affected
| Fixed in– |
CPE configurations (1)
cpe:2.3:a:sourcecodester:student_grades_management_system:*:*:*:*:*:*:*:*
AI-suggested
Until an official fix is released, users should consider implementing CSRF protections such as anti-CSRF tokens or request validation mechanisms. Monitoring for suspicious activity related to unauthorized requests is advisable. No vendor-provided mitigation or official fix is currently documented.
Description
CVE-2026-9486 is a cross-site request forgery (CSRF) vulnerability affecting SourceCodester Student Grades Management System version 1.0. The flaw allows remote attackers to trick authenticated users into submitting unauthorized requests. The vulnerability has a medium severity with a CVSS score of 5.3. No official patch or remediation guidance has been provided by the vendor as of the publication date. Exploit code has been publicly released, increasing the risk of potential attacks. The affected product is not a cloud service, so remediation depends on vendor updates or user-applied fixes.