# CVE-2026-130788: SemanticMediaWiki 3.0.0 before 7.4.0 Reflected XSS via Special:Ask CSV/DSV Separators


- **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:** Yes
- **Published:** 18 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-54fg-5p78-mhg8, GHSA-xc3w-6wv3-fr94

## What is CVE-2026-130788?

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

### Official description

SemanticMediaWiki from 3.0.0 before 7.4.0 contains a reflected cross-site scripting vulnerability in CsvFileExportPrinter and DsvResultPrinter via unescaped valuesep and separator parameters. Attackers can craft Special:Ask links using request_type=special_page so export output renders as text/html, executing JavaScript in victims' browsers under the wiki origin.

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

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


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

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

## Is CVE-2026-130788 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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