# CVE-2026-116883: Semantic MediaWiki 3.1.0 before 7.3.1 Stored XSS via Schema Descriptions


- **Severity:** Medium 4.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/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-2xr9-cr6h-wr6m, GHSA-8v49-wg82-6ffh

## What is CVE-2026-116883?

CVE-2026-116883 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 stored cross-site scripting vulnerability that allows authenticated schema editors to inject HTML through schema descriptions. Attackers with the smw-schemaedit permission can save HTML that is passed unescaped to Html::rawElement() in HtmlBuilder, altering pages and targeting users who view the schema.

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

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


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

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

## Is CVE-2026-116883 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116883 is a medium-severity vulnerability in SemanticMediaWiki, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116883 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-116883/ (Markdown: https://insights.sbomify.com/CVE-2026-116883/index.md)
```

## Sources

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

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