Semantic MediaWiki affected by reflected XSS in Special:Ask via a forged cursor pagination token
CVE-2026-77616GHSA-cx86-7xwp-w9wf
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (mediawiki/semantic-media-wiki 7.2.0), redeploy, then verify what is actually installed.
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.
Affected packages
Packagist mediawiki/semantic-media-wiki
- Affected
- >= 7.0.0, <= 7.1.0
- Fixed in
- 7.2.0
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-cx86-7xwp-w9wf lists affected ranges: Packagist mediawiki/semantic-media-wiki >=7.0.0 <7.2.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-cx86-7xwp-w9wf lists affected ranges: Packagist mediawiki/semantic-media-wiki >=7.0.0 <=7.1.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 6.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
- EPSS
- CVE-2026-77616: 0.33% estimated exploitation activity in the next 30 days; percentile 26.16 (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.
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 sortprop / sortorder 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 sortprop (or…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-cx86-7xwp-w9wf
- Revision 1 · created ·
Published from osv record GHSA-cx86-7xwp-w9wf
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-77616 Advisory: Semantic MediaWiki affected by reflected XSS in `Special:Ask` via a forged cursor pagination token IDs: CVE-2026-77616, GHSA-cx86-7xwp-w9wf Record: https://patchnext.com/advisories/cve-2026-77616 (revision 2, source checked 26 Oct 2026, 14:53 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.1) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: mediawiki/semantic-media-wiki 7.2.0. A vendor fix does not mean a deployment is fixed. ## Affected components - Packagist mediawiki/semantic-media-wiki: affected >= 7.0.0, <= 7.1.0; fixed in 7.2.0 ## Suggested inspection (read-only) - Packagist mediawiki/semantic-media-wiki: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on mediawiki/semantic-media-wiki. - 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-cx86-7xwp-w9wf (OSV record GHSA-cx86-7xwp-w9wf lists affected ranges: Packagist mediawiki/semantic-media-wiki >=7.0.0 <7.2.0 (fixed)) - Verified: https://github.com/advisories/GHSA-cx86-7xwp-w9wf (GitHub-reviewed advisory GHSA-cx86-7xwp-w9wf lists affected ranges: Packagist mediawiki/semantic-media-wiki >=7.0.0 <=7.1.0) Commands are suggestions: review each one before running it.
Loading voting…