Quick answers
- Is CVE-2026-116875 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116875 being exploited in the wild.
- How severe is CVE-2026-116875?
- Medium severity, with a CVSS score of 6.1, published 27 October 2026.
- Which products and versions are affected?
- SemanticMediaWiki 3.0.0 before 7.3.1.
- Is there a fix for CVE-2026-116875?
- Yes: fixed in 7.3.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116875 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-116875?
- Check whether you run SemanticMediaWiki 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.3.1
Technical details
SemanticMediaWiki's Special:Ask page accepts multiple separator parameters (sep, propsep, valuesep, delim, separator) that are reflected without HTML escaping into the response from list, category, DSV, and CSV result printers when request_type=raw or request_type=special_page is used. The vulnerable code paths use raw PHP implode() to join user-controlled separator values into the HTML response, which is served without a Content-Type header, causing the browser to interpret it as text/html. An unauthenticated attacker can inject arbitrary HTML and JavaScript by crafting a Special:Ask URL.
Affected products
- SemanticMediaWiki SemanticMediaWiki 3.0.0 before 7.3.1
Timeline
- 2026-09-28: disclosed
- 2026-10-27: advisory