# CVE-2026-126561: Semantic MediaWiki 2.5.0 before 7.4.1 Missing Authorization via Is edit protected Annotation

> Editors lacking edit rights can lock pages with an annotation, blocking other editors and admins indefinitely; Semantic MediaWiki operators should care.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 11 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-9w3p-9m8x-j2mw, GHSA-vw39-q2rg-9qg8

## What is CVE-2026-126561?

CVE-2026-126561 is a high-severity missing authorization vulnerability in SemanticMediaWiki, published on 11 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Semantic MediaWiki 2.5.0 before 7.4.1 contains a missing authorization vulnerability that allows editors without the edit-protection right to lock pages by adding an Is edit protected annotation. Attackers can add [[Is edit protected::true]] to pages or #set it in widely transcluded templates, so the TitleQuickPermissions hook blocks other editors and administrators from editing, moving or deleting them indefinitely.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-126561?

An affected version is exposed as installed. No special setting or call is needed.


## How do I fix CVE-2026-126561?

No fix has been published for CVE-2026-126561 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-126561 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-126561 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-126561 and fix it if it is affected.

What it is: CVE-2026-126561 is a high-severity missing authorization vulnerability in SemanticMediaWiki, published on 11 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-126561 exists.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: SemanticMediaWiki. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-126561/ (Markdown: https://insights.sbomify.com/CVE-2026-126561/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-126561
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-126561
- OSV: https://osv.dev/vulnerability/CVE-2026-126561

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-126561/
Summaries are generated and may contain mistakes; the official description above is the record.