Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify wiki with extended search engine enabled
-
ExploitPOST ~104KB search term with thousands of in:() filters
-
ImpactQuadratic rescans exhaust PHP search worker CPU
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V2 - Validation and Business Logic Algorithmic complexity limits
|
| Exploitation Conditions | Requires that the wiki is configured to use SMW\MediaWiki\Search\ExtendedSearchEngine (the SMWSearch backend) as its search engine - this is the decisive, non-default precondition; wikis on the default MediaWiki search are not affected. The attacker also needs the server to accept a request body of roughly 104 KB (the demonstrated term size using ~8,000 compact expressions). No authentication is required because public Special:Search is reachable anonymously (PR:N confirmed by the CVSS vector). Limiting factors defenders can lean on: the extended search backend must be explicitly enabled, web-server or PHP request-size/time limits may blunt or prevent the attack, and the demonstrated effect is CPU time in individual workers rather than a proven full-service outage. |
| Impact | Signals point to a genuine but bounded availability risk. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N, availability-only VA:H, score 8.7) describes a remote, unauthenticated, low-complexity denial-of-service against the vulnerable system with no confidentiality or integrity impact - consistent with the CWE-407 algorithmic-complexity root cause. The vendor's VA:H appears optimistic relative to the advisory's own findings: VulnCheck explicitly states it demonstrated 'disproportionate CPU time in a PHP request worker' but did NOT demonstrate a worker crash or service-wide outage, and notes web-server request limits may affect exploitability - so the realistic worst case is worker starvation under concurrency rather than a confirmed full outage. No EPSS score and no CISA KEV entry are provided (absence of KEV means no confirmed active exploitation), and the PoC is a parser-only reproduction rather than a validated end-to-end remote exploit. The vuln.today decision label is 'this_week', not act_now/emergency. Net: a real, patch-this-week availability issue that is materially gated by a non-default configuration (the extended search engine must be enabled), not a high-CVSS-but-illusory finding, but also not an actively-exploited emergency. Key caveat to verify: exploitation is only possible when SMW's ExtendedSearchEngine/SMWSearch backend is configured, which the raw network-vector score does not reflect. |
| Exploit ScenarioDerived | On a public wiki that uses Semantic MediaWiki's extended search backend, an anonymous attacker sends a form POST to index.php?title=Special:Search with a ~104 KB 'search' value packed with thousands of distinct in:(...)/has:(...) compact expressions. TermParser::normalize_compact_form() rescans and copies the whole term once per match, so parsing cost grows quadratically and ties up a PHP search worker; repeated concurrent requests can consume the available workers. A public PoC reference exists (a bounded parser-only reproduction in the GHSA advisory); it is not verified as working end-to-end remote exploit code. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 28, 2026
Quadratic CPU consumption in Semantic MediaWiki's term parser gives unauthenticated visitors a way to tie up PHP search workers on wikis that run the SMW extended search backend. Versions 3.0.0 through 7.3.0 are affected: a search term packed with thousands of distinct in:(...) / has:(...) expressions makes TermParser::normalize_compact_form() rescan and copy the entire input once per match, and the vendor's own parser-only timings show roughly a 4x cost for each doubling of expression count (about 880 ms for an 8,000-expression, ~104 KB term). Signals point to a genuine but bounded availability risk - the extended search engine is a non-default, explicitly enabled backend, request-size or time limits may blunt the attack, and no worker crash or service-wide outage was demonstrated; a public PoC reference exists (a self-contained PHP script that calls the parser directly), it is not verified as working exploit code against a full wiki, and there is no KEV listing or other confirmation of active exploitation.
RemediationAI
Upgrade to Semantic MediaWiki 7.3.1, the vendor-released fix version, which rewrites normalize_compact_form() as a single-pass preg_replace_callback() over the term and enforces a MAX_COMPACT_EXPRESSIONS = 1000 cap per term (commit c2bf1699dec4016e21ce52613152bda799ce87d4, advisory GHSA-j2r2-7qpg-p675). Be aware of the deliberate side effect of the cap: on patched installs, terms carrying more than 1,000 compact in:(...)/has:(...) expressions are left partially unexpanded, which bounds parsing work but changes results for pathologically long queries. If 7.3.1 cannot be deployed immediately, the most direct exposure control is to stop using the SMW extended search backend (SMWSearch / ExtendedSearchEngine) and run the default MediaWiki search until the upgrade lands - this removes the vulnerable code path entirely at the cost of SMW's extended search functionality. Complementary limits only blunt the attack and the vendor treats a request-length guard as an additional defensive measure rather than a replacement for the algorithmic fix: cap accepted request body size at the web server or PHP layer (the demonstrated term was roughly 104 KB, so limits below that prevent the reproduced case), lower PHP max_execution_time and request timeouts for search workers, and rate-limit anonymous requests to index.php?title=Special:Search - each of these risks breaking legitimate large queries or slowing normal search, and none eliminates the quadratic parse once a request is accepted. Vendor references: https://github.com/SemanticMediaWiki/SemanticMediaWiki/security/advisories/GHSA-j2r2-7qpg-p675 and https://github.com/SemanticMediaWiki/SemanticMediaWiki/commit/c2bf1699dec4016e21ce52613152bda799ce87d4.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Semantic MediaWiki adds semantic query syntax to MediaWiki search. When the SMW\MediaWiki\Search\ExtendedSearchEngine backend (alias SMWSearch) is the configured search engine, Special:Search passes the submitted term to SMW's QueryBuilder, which calls TermParser::parse() before query execution (QueryBuilder.php:135-140). Inside TermParser::normalize_compact_form() (TermParser.php:194-231 in the reviewed revision), the code first runs preg_match_all() to collect every compact in:(...) / has:(...) expression in the term, then loops over the matches performing a str_replace() across the whole term for each one, so preprocessing cost grows quadratically with the number of distinct compact expressions and with input length - the CWE-407 algorithmic complexity class. The reachable request shape is a form POST to index.php?title=Special:Search with a roughly 104 KB search field containing ~8,000 distinct compact expressions. Vendor measurements from the parser alone: 1,000 expressions (12,998 bytes) 20.78 ms, 2,000 (25,998 bytes) 57.89 ms, 4,000 (51,998 bytes) 224.06 ms, 8,000 (103,998 bytes) 880.61 ms, with near-4x scaling per doubling from 2,000 onward. The impact is disproportionate CPU time inside individual PHP request workers; concurrent requests could occupy available search workers, but the reporter did not demonstrate a worker crash or a service-wide outage, and web-server request limits may affect exploitability. The upstream fix replaces the repeated str_replace loop with a single-pass preg_replace_callback and adds a MAX_COMPACT_EXPRESSIONS = 1000 cap. This is distinct from GHSA-wh64-r5x2-vjgf (quadratic property-label similarity), which involves a different endpoint, input and algorithm.
Know when Mediawiki gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Remote, unauthenticated, low-complexity request against public Special:Search (AV:N/AC:L/PR:N/UI:N); availability-only and set to A:L because the advisory demonstrated worker CPU exhaustion but not a confirmed full outage.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
Semantic MediaWiki from 3.0.0 before 7.3.1 contains an algorithmic complexity vulnerability in TermParser::normalize_compact_form() that allows unauthenticated attackers to cause quadratic CPU consumption. Attackers can submit long search terms with many distinct in:(...) or has:(...) expressions to Special:Search to exhaust PHP search workers when the extended search engine is enabled.
Executive ViewAI
CVE-2026-116872 exposes Semantic MediaWiki installations using the non-default extended search backend to CPU exhaustion by unauthenticated visitors, potentially degrading search performance and tying up PHP workers. The vulnerability affects versions 3.0.0 through 7.3.0, and while the risk is bounded by the non-default configuration and existing request limits, it could lead to localized availability issues. Leadership should prioritize patching for any wikis running the extended search backend to prevent service disruption.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
MediaWiki 1.22.x before 1.22.2, 1.21.x before 1.21.5, and 1.19.x before 1.19.11, when DjVu or PDF file upload support is
The MWOAuthDataStore::lookup_token function in Extension:OAuth for MediaWiki 1.25.x before 1.25.3, 1.24.x before 1.24.4,
An issue was discovered in the CheckUser extension for MediaWiki through 1.39.3. Rated critical severity (CVSS 9.8), thi
The admin API module in the QuizGame extension for MediaWiki through 1.37.2 (before 665e33a68f6fa1167df99c0aa18ed0157cdf
The SemanticDrilldown extension for MediaWiki through 1.37.2 (before e688bdba6434591b5dff689a45e4d53459954773) allows SQ
An issue was discovered in MediaWiki through 1.37.1. Rated critical severity (CVSS 9.8), this vulnerability is remotely
An issue was discovered in MediaWiki through 1.37.1. Rated critical severity (CVSS 9.8), this vulnerability is remotely
An issue was discovered in the CentralAuth extension in MediaWiki through 1.36. Rated critical severity (CVSS 9.8), this
An issue was discovered in the AbuseFilter extension in MediaWiki through 1.36. Rated critical severity (CVSS 9.8), this
api.php in MediaWiki before 1.27.4, 1.28.x before 1.28.3, and 1.29.x before 1.29.2 has a Reflected File Download vulnera
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in The Wikimedia Foun
An issue was discovered in the FileImporter extension in MediaWiki through 1.36. Rated high severity (CVSS 8.8), this vu
EUVD-2026-110700
GHSA-22p9-pjfx-9wj2
NVD
CVE.org
EPSS
Exploit-DB