# CVE-2026-116885: Semantic MediaWiki before 7.3.1 Reflected XSS via Special:SMWAdmin id Parameter


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-3jj2-qhj9-9w4r, GHSA-4fr3-ghqj-28wx

## What is CVE-2026-116885?

CVE-2026-116885 is a medium-severity vulnerability in SemanticMediaWiki, published on 27 Oct 2026. 

### Official description

Semantic MediaWiki from 3.1.0 before 7.3.1 contains a reflected cross-site scripting vulnerability in the Special:SMWAdmin ID lookup that allows unauthenticated attackers to inject markup through the unescaped id parameter. Attackers can lure an smw-admin administrator into opening a crafted lookup link, bypassing the auto-satisfied edit-token check, to execute script and perform privileged actions in the administrator's session.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-116885 being exploited?

There is no known exploitation of CVE-2026-116885 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116885 is a medium-severity vulnerability in SemanticMediaWiki, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116885 in the wild and no public exploit code.

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

## Sources

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

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