Quick answers
- Is CVE-2026-116876 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116876 being exploited in the wild.
- How severe is CVE-2026-116876?
- High severity, with a CVSS score of 7.1, published 27 October 2026.
- Which products and versions are affected?
- Semantic MediaWiki 2.5.0 before 7.3.1.
- Is there a fix for CVE-2026-116876?
- Yes: fixed in 7.3.1. Until then: Disable the optional edit-protection feature by not setting $smwgEditProtectionRight, or restrict it to highly trusted user groups only. Ensure $smwgEditProtectionRight is set to a right held only by curators or administrators, not ordinary editors. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116876 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-116876?
- Check whether you run 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.3.1
Disable the optional edit-protection feature by not setting $smwgEditProtectionRight, or restrict it to highly trusted user groups only. Ensure $smwgEditProtectionRight is set to a right held only by curators or administrators, not ordinary editors.
Technical details
The vulnerability is an authorization bypass in the EditProtectionUpdater component. When a page edit includes the "Is edit protected::true" annotation, the updater applies indefinite edit and move restrictions without verifying that the author holds the configured smwgEditProtectionRight. An unauthenticated editor can exploit this via a network-based page edit to lock pages indefinitely, requiring the edit-protection feature to be enabled with a configured protection right.
Affected products
- Semantic MediaWiki Semantic MediaWiki 2.5.0 before 7.3.1
Timeline
- 2026-09-28: disclosed
- 2026-09-28: patched: Fix released in version 7.3.1
- 2026-10-27: advisory