← Back
CVE-2026-54049
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). Risk of unauthorized operations or information disclosure. Exploitable via `POST /api/sites/{siteId}/topics`.
AI summary snake-internal / snake-material-v2
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.
Risk of unauthorized operations or information disclosure. CVSS score: ?/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 /
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` without authentication.
📍 Affected scope
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: ?. Risk of unauthorized operations or information disclosure
🔧 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. Run `grep -r 'org.sakaiproject.conversations:sakai-conversations-impl' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'org.sakaiproject.conversations:sakai-conversations-impl' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.sakaiproject.conversations:sakai-conversations-impl` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt 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 があれば該当パスのアラート発火履歴を確認。
-
7Post-deployment verification verify
Replay attack against POST /api/sites/{siteId}/topics on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
org.sakaiproject.conversations:sakai-conversations-impl
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
maven
org.sakaiproject.kernel:sakai-kernel-impl
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
maven
org.sakaiproject.rubrics:rubrics-impl
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]