# CVE-2026-130789: SemanticMediaWiki 7.3.0 before 7.4.0 Missing Authorization in smwtask check-query


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-8h27-4cx8-59hx, GHSA-qhqw-xc5w-pp27

## What is CVE-2026-130789?

CVE-2026-130789 is a medium-severity vulnerability in SemanticMediaWiki, published on 18 Nov 2026. 

### Official description

SemanticMediaWiki from 7.3.0 before 7.4.0 contains a missing authorization vulnerability in the smwtask API check-query task that allows unauthenticated attackers to bypass object-level authorization by relying on the wiki-wide edit right. Attackers can supply arbitrary subject titles, including protected pages, to run synchronous Semantic MediaWiki queries with caller-controlled conditions, limit, offset, and querymode parameters.

Weakness: CWE-862 (Missing Authorization)

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


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

Upgrade SemanticMediaWiki to 7.4.0 or later. The advisory says that version fixes it.

## Is CVE-2026-130789 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130789 is a medium-severity vulnerability in SemanticMediaWiki, published on 18 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-130789 exists.

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-130789/ (Markdown: https://insights.sbomify.com/CVE-2026-130789/index.md)
```

## Sources

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

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