Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.7amended

Sakai Conversations has a Stored XSS Issue

CVE-2026-54049GHSA-w2x5-gv52-9ccv

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Maven org.sakaiproject.conversations:sakai-conversations-impl

    Affected
    >= 23.0, <= 23.3
    Fixed in
    no fixed version recorded

  • Maven org.sakaiproject.kernel:sakai-kernel-impl

    Affected
    >= 23.0, <= 23.3
    Fixed in
    no fixed version recorded

  • Maven org.sakaiproject.rubrics:rubrics-impl

    Affected
    >= 23.0, <= 23.3
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
EPSS
  • CVE-2026-54049: 0.32% estimated exploitation activity in the next 30 days; percentile 25.37 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary 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. Description The Conversations REST API endpoint POST /api/sites/{siteId}/topics accepts a message field in the JSON request body. The service layer (ConversationsServiceImpl) stores the message directly to the database (convtopics.MESSAGE) without invoking FormattedText.processFormattedText() or any equivalent HTML sanitizer. The same issue affects post replies via POST /api/sites/{siteId}/topics/{topicId}/posts and comments stored in convcomments. On the frontend, SakaiTopic.js, SakaiPost.js, and SakaiComment.js all render the message field using LitElement's…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-w2x5-gv52-9ccv

  2. Revision 1 · created ·

    Published from osv record GHSA-w2x5-gv52-9ccv

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54049

Advisory: Sakai Conversations has a Stored XSS Issue
IDs: CVE-2026-54049, GHSA-w2x5-gv52-9ccv
Record: https://patchnext.com/advisories/cve-2026-54049 (revision 2, source checked 26 Oct 2026, 16:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.sakaiproject.conversations:sakai-conversations-impl: affected >= 23.0, <= 23.3
- Maven org.sakaiproject.kernel:sakai-kernel-impl: affected >= 23.0, <= 23.3
- Maven org.sakaiproject.rubrics:rubrics-impl: affected >= 23.0, <= 23.3

## Suggested inspection (read-only)
- Maven org.sakaiproject.conversations:sakai-conversations-impl: check the installed version with your package manager.
- Maven org.sakaiproject.kernel:sakai-kernel-impl: check the installed version with your package manager.
- Maven org.sakaiproject.rubrics:rubrics-impl: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.sakaiproject.conversations:sakai-conversations-impl, org.sakaiproject.kernel:sakai-kernel-impl, org.sakaiproject.rubrics:rubrics-impl.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-w2x5-gv52-9ccv (OSV record GHSA-w2x5-gv52-9ccv lists affected ranges: Maven org.sakaiproject.conversations:sakai-conversations-impl >=23.0 =23.0 =23.0 <=23.3)
- Verified: https://github.com/advisories/GHSA-w2x5-gv52-9ccv (GitHub-reviewed advisory GHSA-w2x5-gv52-9ccv lists affected ranges: Maven org.sakaiproject.conversations:sakai-conversations-impl >=23.0 =23.0 =23.0 <=23.3)

Commands are suggestions: review each one before running it.

Loading voting…