Quick answers
- Is CVE-2026-126567 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-126567 being exploited in the wild.
- How severe is CVE-2026-126567?
- Medium severity, with a CVSS score of 5.4, published 11 November 2026.
- Which products and versions are affected?
- SemanticMediaWiki Semantic MediaWiki 3.0.0 to before 7.4.1.
- Is there a fix for CVE-2026-126567?
- Yes: fixed in 7.4.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-126567 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-126567?
- Check whether you run SemanticMediaWiki Semantic MediaWiki at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 7.4.1
Technical details
A stored XSS vulnerability exists in the Special:Ask page when using the ElasticStore backend, where user-controlled data from Text properties and subobject names is output without proper HTML escaping in the native_result and score_set displays. An attacker with edit rights can store malicious markup in wiki properties, then craft a Special:Ask URL that triggers the vulnerable code path and causes the injected script to execute in the victim's browser session.
Affected products
- SemanticMediaWiki Semantic MediaWiki 3.0.0 to before 7.4.1
Timeline
- 2026-11-11: disclosed