CVE-2026-2201

2.4 LOW

📋 TL;DR

This CVE describes a cross-site scripting (XSS) vulnerability in ZeroWdd studentmanager's leave request functionality. Attackers can inject malicious scripts via the 'Reason for Leave' parameter, potentially compromising user sessions. The vulnerability affects all versions up to commit 2151560fc0a50ec00426785ec1e01a3763b380d9.

💻 Affected Systems

Products:
  • ZeroWdd studentmanager
Versions: All versions up to commit 2151560fc0a50ec00426785ec1e01a3763b380d9
Operating Systems: Any OS running Java applications
Default Config Vulnerable: ⚠️ Yes
Notes: The project uses rolling releases and the repository has been inactive for years, making version tracking difficult.

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could steal session cookies, perform actions as authenticated users, redirect to malicious sites, or install malware on user systems.

🟠

Likely Case

Session hijacking, credential theft, or defacement of the application interface.

🟢

If Mitigated

Limited impact with proper input validation and output encoding in place.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploit details are publicly available, and XSS attacks are commonly weaponized in real-world attacks.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Not available

Vendor Advisory: Not available

Restart Required: No

Instructions:

No official patch exists. Consider implementing input validation and output encoding in the LeaveController.java file, specifically in the addLeave function.

🔧 Temporary Workarounds

Input Validation and Output Encoding

all

Implement server-side validation of the 'Reason for Leave' parameter and encode all user-controlled output.

Content Security Policy

all

Implement a strict Content Security Policy header to mitigate XSS impact.

🧯 If You Can't Patch

  • Implement a web application firewall (WAF) with XSS protection rules
  • Disable or restrict access to the vulnerable leave request functionality

🔍 How to Verify

Check if Vulnerable:

Test by submitting a script payload (e.g., <script>alert('XSS')</script>) in the 'Reason for Leave' field and check if it executes.

Check Version:

Check the git commit hash or version metadata in the application.

Verify Fix Applied:

After implementing fixes, test with the same payload to ensure it's properly sanitized or blocked.

📡 Detection & Monitoring

Log Indicators:

  • Unusual or long strings in leave request logs containing script tags or JavaScript

Network Indicators:

  • HTTP requests with script payloads in parameters

SIEM Query:

source="application_logs" AND ("<script>" OR "javascript:" OR "onerror=" OR "onload=")

🔗 References

📤 Share & Export