Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.3amended

Semantic MediaWiki'a missing authorization in the smwtask API module allows unauthenticated access to admin-only maintenance tasks

CVE-2026-116890GHSA-jr78-w6w5-m8f8

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (mediawiki/semantic-media-wiki 7.3.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.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
EPSS
  • CVE-2026-116890: 0.19% estimated exploitation activity in the next 30 days; percentile 8.80 (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.

Summary The `api.php?action=smwtask` API module performs no authorization check. The equivalent maintenance interface in the web UI (`Special:SMWAdmin`) requires the `smw-admin` right, but the API module that backs several of the same operations enforces nothing. An unauthenticated visitor can therefore retrieve internal Semantic MediaWiki database statistics and reach state-changing maintenance operations that are intended to be administrator-only.

Details `SMW\MediaWiki\Api\Task::execute()` (`src/MediaWiki/Api/Task.php`) reads the request parameters, resolves a task through `TaskFactory`, and runs it. It contains no permission check — no `smw-admin`, no `checkUserRightsAny()`, no per-task right. The only gates on the module are: - `needsToken( 'csrf' )` — this is not authorization. MediaWiki issues anonymous users a fixed, public CSRF token (`+\`), so any unauthenticated caller satisfies the token check. It defends logged-in users against CSRF; it does nothing against a…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from osv record GHSA-jr78-w6w5-m8f8

  2. Revision 2 · amended ·

    Amended from ghsa record GHSA-jr78-w6w5-m8f8

  3. Revision 1 · created ·

    Published from osv record GHSA-jr78-w6w5-m8f8

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-116890

Advisory: Semantic MediaWiki'a missing authorization in the smwtask API module allows unauthenticated access to admin-only maintenance tasks
IDs: CVE-2026-116890, GHSA-jr78-w6w5-m8f8
Record: https://patchnext.com/advisories/ghsa-jr78-w6w5-m8f8 (revision 3, source checked 28 Oct 2026, 06:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.3)
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.3.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist mediawiki/semantic-media-wiki: affected >= 3.0.0, < 7.3.0; fixed in 7.3.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-jr78-w6w5-m8f8 (OSV record GHSA-jr78-w6w5-m8f8 lists affected ranges: Packagist mediawiki/semantic-media-wiki >=3.0.0 <7.3.0 (fixed))
- Verified: https://github.com/advisories/GHSA-jr78-w6w5-m8f8 (GitHub-reviewed advisory GHSA-jr78-w6w5-m8f8 lists affected ranges: Packagist mediawiki/semantic-media-wiki >=3.0.0 <=7.2.1)

Commands are suggestions: review each one before running it.

Loading voting…