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

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

Summary

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

Original description

The description as published by the source.

Query debug output XSS

Failure mode

Semantic MediaWiki's query debug output (format=debug, or the debug request parameter on Special:Ask) is assembled by SMW\Query\DebugFormatter and emitted as raw HTML. Several of its sinks apply no output-context encoding, so attacker-controlled query input is reflected into the page without escaping:

  • buildHTML() echoes the re-serialized ASK query string escaping only [; <, >, ", ' pass through.
  • prettifySQL() returns the generated SQL verbatim. Query value literals are inlined into the SQL through the database layer's quoting (SQL-escaping only, no HTML encoding), so markup in a value survives.
  • prettifyExplain() echoes EXPLAIN output; on PostgreSQL the plan text contains the WHERE literals.

On Special:Ask the resulting string is concatenated into the page and sent through OutputPage::addHTML, never through the MediaWiki parser or Sanitizer. No special user right is required; an anonymous request suffices.

This is a reflected XSS: the payload is taken from the request and echoed in the same response. Exploitation requires the query condition to target a text/blob-typed property (whose value is re-serialized verbatim); the predefined _txt properties (Text, etc.) that ship on every install satisfy this, so no attacker-created content is needed. Example request:

Special:Ask?q=[[Text::alert(document.domain)]]&debug=1

Remediation

  • Apply output-context escaping at the `DebugFo…

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-77610 has been found in mediawiki/semantic-media-wiki.
Attackers can target a specific entry point like debug 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-77610" on the vendor's site.

CVE-2026-77610 (mediawiki/semantic-media-wiki) — CWE-79 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: debug / EXPLAIN / WHERE / _txt
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 debug without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of mediawiki/semantic-media-wiki. Attack surface: debug / EXPLAIN / WHERE / _txt.

🔥 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