CVE-2026-54049
| Severity | 8.7 High CVSS 3.1 |
|---|---|
| Weakness | Cross-site scripting (CWE-79) |
| Published | 1 Oct 2026 |
| Updated | 6 Oct 2026 |
Published 43 days ago. NVD often adds the list of affected products days or weeks after a CVE is published, and the other sources we check lag too. The scope and status here may change.
Description
Sakai is a Collaboration and Learning Environment (CLE). From versions 23.0 to before 23.5, and versions 25.0 to before 25.3, the Sakai Conversations tool stores topic and post messages without HTML sanitization, and the frontend renders them using LitElement's unsafeHTML() directive, resulting in stored cross-site scripting (XSS). Any authenticated user with access to a site that has the Conversations tool enabled can inject arbitrary HTML and JavaScript that executes in the browsers of all other users who view that topic or post. This issue has been patched in versions 23.5, 25.3, and 26.0.
Exploitation status
Proof of concept only
A proof of concept exists, but no reviewed exploit catalogue lists this CVE.
Exploitation status
- CISA KEV not listed
- VulnCheck KEV not listed
- CISA Vulnrichment exploitation: poc CISA recorded that an exploit has been demonstrated. Automatable: no, technical impact: total.
- Indexed PoC none indexed
- EPSS 0.32% chance in 30 days
Waratek protection
Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.
A public code fix exists: sakaiproject/sakai 2696b4b.
- Protection none
- Action unverified
- Review automated Upstream data
- Record active
| Decided by | Exploit code for this candidate, published in a reviewed catalogue or a GitHub repository with 5 or more stars, or in use per CISA or VulnCheck; not only a CISA verdict, a forecast, or nothing at all |
|---|---|
| Finding | This CVE is not listed in CISA KEV or VulnCheck KEV, CISA Vulnrichment records no active exploitation, no reviewed exploit catalogue carries an entry for it, and no GitHub PoC repository for it has 5 or more stars. Nobody has published exploit code worth tracing, so it is not a candidate for a rule ahead of the ones where somebody has; an upstream fix path does exist, so the remediation half of the candidacy still holds. This is a statement about what has been published, not about whether the defect is reachable or serious. |
| Candidate fix | https://github.com/sakaiproject/sakai/commit/2696b4b48cbef2e81512f52f84f7477adff78b27 : a commit: the change itself |
Affected software and releases
Maven packages
Affected and fixed versions, from OSV.dev| Package | Introduced | Fixed | Last affected |
|---|---|---|---|
org.sakaiproject.conversations:sakai-conversations-impl |
23.0 | none | 23.3 |
org.sakaiproject.kernel:sakai-kernel-impl |
23.0 | none | 23.3 |
org.sakaiproject.rubrics:rubrics-impl |
23.0 | none | 23.3 |
Products and versions
3 products, 3 version entries| Source | Vendor | Product | Scheme | Affected versions |
|---|---|---|---|---|
| osv | org.sakaiproject.conversations | sakai-conversations-impl | generic | ≥ 23.0 and ≤ 23.3 |
| osv | org.sakaiproject.kernel | sakai-kernel-impl | generic | ≥ 23.0 and ≤ 23.3 |
| osv | org.sakaiproject.rubrics | rubrics-impl | generic | ≥ 23.0 and ≤ 23.3 |
References
Timeline
Timeline
| Published | 2026-10-01 | By the CVE Program. |
|---|---|---|
| NVD record modified | 2026-10-06 | NVD's own last-modified date for this record. |