CVE-2026-33402: sakaiproject sakai · Cross-site Scripting
Affects sakaiproject sakaiSource CVE Database V5
Not known to be exploited · CVSS 1.3 Low : upgrade to 25.2 or 23.5 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 25.2, 23.5
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:UExploitation evidence
Disclosed: evidence found.
CVE published 26 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 Oct 2026.
What to do
Upgrade sakaiproject sakai to 25.2 or 23.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| sakaiprojectsakai | Affected
| Fixed in
|
| sakaiprojectsakai | Affected
| Fixed in
|
GitHubsakaiproject/sakaipkg:github/sakaiproject/sakaiOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Apply official patches by upgrading Sakai to versions 23.5 or 25.2 or later, which include fixes for this XSS vulnerability.
- As an immediate workaround, audit the SAKAI_SITE_GROUP database table for group titles and descriptions containing suspicious or script-like content, and sanitize or remove such entries.
- Implement Content Security Policy (CSP) headers to restrict the execution of inline scripts and reduce the impact of potential XSS attacks.
- Educate users to be cautious when interacting with group pages and to report suspicious behavior.
- Regularly monitor web application logs and user reports for signs of attempted exploitation or unusual activity.
- Consider deploying web application firewalls (WAFs) with rules to detect and block common XSS payloads targeting Sakai.
- Review and harden input validation and output encoding practices in custom Sakai deployments or integrations to prevent similar vulnerabilities.
Description
Sakai is a Collaboration and Learning Environment (CLE). In versions 23.0 through 23.4 and 25.0 through 25.1, group titles and description can contain cross-site scripting scripts. The patch is included in releases 25.2 and 23.5. As a workaround, one can check the SAKAI_SITE_GROUP table for titles and descriptions that contain this info.