CVE-2026-33402
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSakai 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a stored XSS vulnerability in Sakai's group management feature where group titles and descriptions are not properly sanitized before being stored and rendered, allowing attackers to inject malicious JavaScript that executes when other users view these group entries.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 23.0, < 23.5>= 25.0, < 25.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Sakai versionCheck the Sakai version by reviewing the build configuration file (pom.xml or sakai-version.properties) in the deployment, or query the database: SELECT VALUE FROM SAKAI_PROPERTY WHERE NAME='version.release'Affected if The installed version is >= 23.0 and < 23.5, OR >= 25.0 and < 25.2
-
Verify group management feature is in useQuery the database to confirm groups exist: SELECT COUNT(*) FROM SAKAI_SITE_GROUP WHERE SITE_ID IS NOT NULLAffected if Groups exist in the system - the vulnerability only applies when the group management feature is being used
-
Inspect group titles for suspicious contentQuery the SAKAI_SITE_GROUP table for potential XSS payloads in the TITLE column: SELECT GROUP_ID, TITLE, CREATOR_ID, CREATION_DATE FROM SAKAI_SITE_GROUP WHERE TITLE LIKE '%<script%' OR TITLE LIKE '%javascript:%' OR TITLE LIKE '%onerror=%' OR TITLE LIKE '%onload=%'Affected if Any rows are returned containing script tags, javascript: URIs, or event handlers like onerror or onload in the title
-
Inspect group descriptions for suspicious contentQuery the SAKAI_SITE_GROUP table for potential XSS payloads in the DESCRIPTION column: SELECT GROUP_ID, DESCRIPTION, CREATOR_ID, CREATION_DATE FROM SAKAI_SITE_GROUP WHERE DESCRIPTION LIKE '%<script%' OR DESCRIPTION LIKE '%javascript:%' OR DESCRIPTION LIKE '%onerror=%' OR DESCRIPTION LIKE '%onload=%'Affected if Any rows are returned containing script tags, javascript: URIs, or event handlers like onerror or onload in the description
A user is affected if they run a Sakai version within the vulnerable ranges AND have groups with malicious content stored in the TITLE or DESCRIPTION fields of the SAKAI_SITE_GROUP table.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped23.525.2
Upgrade to Sakai versions 25.2 or 23.5 which contain the patch. As a workaround, query the SAKAI_SITE_GROUP database table to identify and remove existing malicious entries in titles and descriptions.
Sakai 23.5 (for 23.x branch) or Sakai 25.2 (for 25.x branch)
- Identify current Sakai version by checking the sakai.properties file or Sakai administration console
- If running version >= 23.0 and < 23.5, plan upgrade to Sakai 23.5
- If running version >= 25.0 and < 25.2, plan upgrade to Sakai 25.2
- Review Sakai upgrade documentation for your current version
- Perform database backup before upgrade
- Execute upgrade process following Sakai upgrade guide
- Verify upgrade by logging into the administration console
- As a secondary verification (optional), query the SAKAI_SITE_GROUP table: SELECT GROUP_ID, TITLE, DESCRIPTION FROM SAKAI_SITE_GROUP WHERE TITLE LIKE '%<script%' OR DESCRIPTION LIKE '%<script%' to ensure no XSS payloads remain
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33402 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-33402 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data