Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-77616 medium CVSS 6.1

Cross-Site Scripting (XSS) in mediawiki/semantic-media-wiki (CVE-2026-77616)

Summary

Cross-site scripting in mediawiki/semantic-media-wiki (CVE-2026-77616). Risk of unauthorized operations or information disclosure. Exploitable via cursor. Mitigation: upgrade to 7.2.0 or later.

Original description

The description as published by the source.

Reflected XSS via a forged cursor pagination token

Failure mode

Special:Ask accepts a cursor query parameter for keyset pagination (added in 7.0.0). The token is decoded by CursorEncoder, which is an unsigned base64url-encoded JSON blob, so its contents are fully attacker-controlled. When the cursor's sort anchor does not match the request's sort= / order=, QueryCreator::applyCursorIfRequested() builds an error message by interpolating the attacker-controlled sort_prop / sort_order values into a raw string via Query::addErrors().

Unlike SMW's message-key errors, this raw string bypasses the message layer's sanitisation (ProcessingErrorMsgHandler::normalizeAndDecodeMessages() passes a non-key, non-encoded string through unchanged). ErrorWidget::queryError() then assembles the errors and passes them to Html::errorBox(), whose first argument is emitted as raw HTML. The result is a reflected cross-site scripting vulnerability: a crafted cursor token containing markup in sort_prop (or sort_order) executes script in the victim's browser on the wiki origin.

No authentication or special permission is required. The payload is delivered via a crafted link, e.g. Special:Ask?q=...&p[cursor]= where the token decodes to {"v":1,"sort_prop":"..."}. Confirmed executing in a browser; the responses carry no Content-Security-Policy, so inline script is not blocked.

Remediation

  • Output-encode the attacker-controlled sort_prop / `sort_ord…

Source: NIST National Vulnerability Database 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-77616 has been found in mediawiki/semantic-media-wiki.
Attackers can target a specific entry point like cursor over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/10.
What to do: upgrade mediawiki/semantic-media-wiki to 7.2.0 or later.
If unsure, ask your IT team or search "mediawiki/semantic-media-wiki CVE-2026-77616" on the vendor's site.

CVE-2026-77616 (mediawiki/semantic-media-wiki) — CWE-79 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: cursor / CursorEncoder / sort_prop / sort_order
Patched: 7.2.0 — apply immediately
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 mediawiki/semantic-media-wiki. Attackers reach the vulnerable code path via cursor without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of mediawiki/semantic-media-wiki. Attack surface: cursor / CursorEncoder / sort_prop / sort_order.

🔥 Severity

Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 7.2.0.

🛡️ 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 request patterns matching this CVE's known IOCs. Run grep -r 'mediawiki/semantic-media-wiki' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

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

  1. 1
    Identify exposure identify 
    grep -r 'mediawiki/semantic-media-wiki' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で mediawiki/semantic-media-wiki を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade mediawiki/semantic-media-wiki to 7.2.0

    ステージング環境で 7.2.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

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

Affected packages

composer mediawiki/semantic-media-wiki
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.2.0"}]}]

References

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