Skip to main content
VulnerabilityPublished

CVE-2026-33402: sakaiproject sakai · Cross-site Scripting

Affects sakaiproject sakaiSource CVE Database V5

0
Compare

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

CVSS 4.0 base score
1.3Low
How severe the flaw is on the 0–10 CVSS scale.
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:U

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
sakaiprojectsakaiAffected
  • >=25.0 <25.2
Fixed in
  • 25.2
sakaiprojectsakaiAffected
  • >=23.0 <23.5
Fixed in
  • 23.5
GitHubsakaiproject/sakaipkg:github/sakaiproject/sakaiOther threatsAffected
  • 23.0 <=23.4
  • 25.0 <=25.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Apply official patches by upgrading Sakai to versions 23.5 or 25.2 or later, which include fixes for this XSS vulnerability.
  2. 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.
  3. Implement Content Security Policy (CSP) headers to restrict the execution of inline scripts and reduce the impact of potential XSS attacks.
  4. Educate users to be cautious when interacting with group pages and to report suspicious behavior.
  5. Regularly monitor web application logs and user reports for signs of attempted exploitation or unusual activity.
  6. Consider deploying web application firewalls (WAFs) with rules to detect and block common XSS payloads targeting Sakai.
  7. 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.

References

Community reviews

Loading reviews…