VulnerabilityPublished 2 Mar 2026

CVE-2026-3403: PHPGurukul Student Record Management System · Cross-site Scripting

Affects PHPGurukul Student Record Management SystemSource CVE Database V5

Compare

Public exploit available · CVSS 4.8 Medium.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score

4.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Mar 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 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
PHPGurukulStudent Record Management System	Affected =1.0	Fixed in–

AI-suggested

To mitigate CVE-2026-3403, organizations should implement strict input validation and output encoding on the 'Subject 1' parameter within the /edit-subject.php script to neutralize malicious scripts. Employing Content Security Policy (CSP) headers can help restrict the execution of unauthorized scripts. Web Application Firewalls (WAFs) should be configured to detect and block XSS attack patterns targeting this parameter. User education on recognizing phishing attempts and suspicious links can reduce the risk of exploitation via social engineering. Regular security assessments and code reviews of the application should be conducted to identify and remediate similar vulnerabilities. Monitoring web server logs for unusual input patterns targeting the 'Subject 1' parameter can provide early detection of exploitation attempts.

Description

A vulnerability was detected in PHPGurukul Student Record Management System 1.0. This issue affects some unknown processing of the file /edit-subject.php. Performing a manipulation of the argument Subject 1 results in cross site scripting. The attack is possible to be carried out remotely. The exploit is now public and may be used.

Impact

The impact of CVE-2026-3403 on organizations primarily involves the compromise of user sessions and the integrity of the web application interface. Successful exploitation could lead to unauthorized access to sensitive student data, manipulation of displayed information, and phishing attacks targeting staff or students. This can damage the reputation of educational institutions, lead to data privacy violations, and potentially result in regulatory penalties depending on jurisdiction. While the vulnerability does not directly allow system-level compromise or data exfiltration, the indirect effects such as credential theft or session hijacking can facilitate further attacks. Organizations relying on PHPGurukul Student Record Management System version 1.0 are at risk, especially if they have not implemented compensating controls. The medium severity rating suggests that while the threat is not critical, it should not be ignored due to the potential for social engineering and trust exploitation.

Summary

CVE-2026-3403 identifies a cross-site scripting vulnerability in the PHPGurukul Student Record Management System version 1.0, specifically in the /edit-subject.php script. The vulnerability arises from insufficient input validation or output encoding of the 'Subject 1' parameter, which allows an attacker to inject arbitrary JavaScript code. This XSS flaw can be exploited remotely without authentication, but requires user interaction to execute the malicious payload, such as tricking a user into clicking a crafted link or submitting manipulated data. The vulnerability could enable attackers to perform session hijacking, steal cookies, deface web pages, or conduct phishing attacks within the context of the affected web application. The CVSS 4.8 score reflects a medium severity, factoring in the network attack vector, low complexity, no privileges required, but requiring user interaction. No official patches or fixes have been released yet, and no active exploits have been reported in the wild. The vulnerability affects only version 1.0 of the product, which is primarily used in educational institutions for managing student records. Given the nature of the vulnerability, attackers could leverage it to compromise user trust and potentially escalate attacks if combined with other vulnerabilities.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Mar 2026, 17:24 UTC

Technical details

References

Community reviews

Related threats