Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-54049 high CVSS 8.7

Cross-Site Scripting (XSS) in org.sakaiproject.conversations:sakai-conversations-impl (CVE-2026-54049)

Summary

Cross-site scripting in org.sakaiproject.conversations:sakai-conversations-impl (CVE-2026-54049). Confidential information can be exposed externally. Exploitable via POST /api/sites/{siteId}/topics.

Original description

The description as published by the source.

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 (conv_topics.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 conv_comments.

On the frontend, SakaiTopic.js, SakaiPost.js, and SakaiComment.js all render the message field using LitElement's unsafeHTML() directive:

  • SakaiPost.js lines 429, 432: ${unsafeHTML(this.post.message)}
  • SakaiTopic.js line 679: ${unsafeHTML(this.topic.message)}
  • SakaiComment.js line 148: ${unsafeHTML(this.comment.message)}

Unlike other Sakai tools (Announcements, Assignments, Resources) which call FormattedText.processFormattedText() before persisting user content, the Conversations implementation has no equivalent protection at storage time or render time.

###…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-54049 has been found in org.sakaiproject.conversations:sakai-conversations-impl.
Attackers can target a specific entry point like POST /api/sites/{siteId}/topics over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "org.sakaiproject.conversations:sakai-conversations-impl CVE-2026-54049" on the vendor's site.

CVE-2026-54049 (org.sakaiproject.conversations:sakai-conversations-impl) — CWE-79 / CVSS v3 8.7
Attack vector: remote (network-reachable)
Attack surface: POST /api/sites/{siteId}/topics / POST /api/sites/{siteId}/topics/{topicId}/posts / POST /api/sites/BELP_275K_7418/topics / POST /api/sites/BELP_275K_7418/topics/e4c599c2-bd32-4364-9cbd-a5c9c102edfb/posts
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in org.sakaiproject.conversations:sakai-conversations-impl. Attackers reach the vulnerable code path via POST /api/sites/{siteId}/topics.

📍 Affected scope

Check the vendor advisory for the affected versions of org.sakaiproject.conversations:sakai-conversations-impl. Attack surface: POST /api/sites/{siteId}/topics / POST /api/sites/{siteId}/topics/{topicId}/posts / POST /api/sites/BELP_275K_7418/topics / POST /api/sites/BELP_275K_7418/topics/e4c599c2-bd32-4364-9cbd-a5c9c102edfb/posts.

🔥 Severity

Severity: High (CVSS 8.7/10). Confidential information can be exposed externally.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual POST /api/sites/{siteId}/topics requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.sakaiproject.conversations:sakai-conversations-impl を使っているサービスとバージョンを洗い出す。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'POST /api/sites/{siteId}/topics' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /api/sites/{siteId}/topics への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Post-deployment verification verify 
    Replay attack against POST /api/sites/{siteId}/topics on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

maven org.sakaiproject.conversations:sakai-conversations-impl
[{"type":"ECOSYSTEM","events":[{"introduced":"23.0"},{"last_affected":"23.3"}]}]
maven org.sakaiproject.kernel:sakai-kernel-impl
[{"type":"ECOSYSTEM","events":[{"introduced":"23.0"},{"last_affected":"23.3"}]}]
maven org.sakaiproject.rubrics:rubrics-impl
[{"type":"ECOSYSTEM","events":[{"introduced":"23.0"},{"last_affected":"23.3"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details