CVE-2026-2201VulnerabilityPublished 9 Feb 2026Updated 23 Feb 2026

CVE-2026-2201: ZeroWdd studentmanager · Cross Site Scripting

Affects ZeroWdd studentmanagerSource CVE Database V5

Not known to be exploited · CVSS 4.8 Medium.

Data as of 25 Oct 2026, 19:02 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 16% 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 9 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC 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
ZeroWddstudentmanager	Affected =2151560fc0a50ec00426785ec1e01a3763b380d9	Fixed in–

CPE configurations (1)

cpe:2.3:a:zerowdd:studentmanager:*:*:*:*:*:*:*:*

AI-suggested

To mitigate CVE-2026-2201, organizations should implement strict input validation and output encoding on the 'Reason for Leave' parameter to neutralize malicious scripts. Employing context-aware encoding (e.g., HTML entity encoding) before rendering user input in web pages is critical. If source code modification is possible, developers should sanitize inputs using established libraries or frameworks that prevent XSS. Deploying a Web Application Firewall (WAF) with rules to detect and block XSS payloads can provide an additional protective layer. Given the inactivity of the official code repository, organizations should consider migrating to actively maintained alternatives or forks. User education to recognize phishing attempts and suspicious links can reduce the risk of exploitation via social engineering. Regular security assessments and penetration testing focused on web application vulnerabilities are recommended. Monitoring logs for unusual input patterns or error messages related to the addLeave function can help detect exploitation attempts early.

Description

A security vulnerability has been detected in ZeroWdd studentmanager up to 2151560fc0a50ec00426785ec1e01a3763b380d9. This impacts the function addLeave of the file src/main/java/com/wdd/studentmanager/controller/LeaveController.java. The manipulation of the argument Reason for Leave leads to cross site scripting. The attack may be initiated remotely. The exploit has been disclosed publicly and may be used. This product uses a rolling release model to deliver continuous updates. As a result, specific version information for affected or updated releases is not available. The code repository of the project has not been active for many years.

Impact

The primary impact of this XSS vulnerability is on the confidentiality and integrity of user sessions and data within the ZeroWdd studentmanager application. Attackers can execute arbitrary scripts in the context of authenticated users, potentially stealing session tokens, personal information, or performing unauthorized actions. This can lead to account compromise, data leakage, and reputational damage for organizations using the software. Since the application is likely used in educational environments to manage student leave records, exposure could disrupt administrative processes and erode trust. The lack of active maintenance and patch availability increases the risk of prolonged exposure. While availability impact is minimal, the integrity and confidentiality risks are significant enough to warrant attention. Organizations worldwide using this software or its derivatives face potential targeted attacks, especially if attackers craft phishing campaigns exploiting this vulnerability.

Summary

CVE-2026-2201 identifies a cross-site scripting (XSS) vulnerability in the ZeroWdd studentmanager application, affecting versions up to commit 2151560fc0a50ec00426785ec1e01a3763b380d9. The flaw exists in the addLeave function within the LeaveController.java source file, where the 'Reason for Leave' input parameter is not properly sanitized or encoded before being reflected in the web interface. This allows an attacker to inject arbitrary JavaScript code that executes in the context of the victim's browser when they view the affected page. The vulnerability can be exploited remotely without authentication, but requires user interaction such as clicking a malicious link or submitting a crafted form. The product follows a rolling release model for updates; however, the code repository has been inactive for years, indicating that official patches or updates may not be forthcoming. The CVSS 4.0 score of 4.8 reflects a medium severity, considering the ease of remote exploitation but limited impact on confidentiality and availability. The vulnerability could be leveraged to steal session cookies, perform actions on behalf of users, or deface the web interface. No known exploits are currently observed in the wild, but public disclosure increases the risk of exploitation attempts.

References

Community reviews

Loading reviews…