# CVE-2025-11184: Cross-Site Scripting Vulnerability in QWC2 Registration GUI

> An authorized attacker can inject arbitrary JavaScript into the QWC2 Registration GUI, potentially compromising user sessions or data.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/AU:N/RE:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Oct 2025
- **Updated:** 14 Oct 2025
- **Also known as:** GHSA-qhh9-jphj-p4xw

## What is CVE-2025-11184?

CVE-2025-11184 is a medium-severity cross-site scripting vulnerability in qwc-services qwc-registration-gui, published on 13 Oct 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting vulnerability in QGIS QWC2 Registration GUI <=v2025.03.31
allows an authorized attacker to plant arbitrary JavaScript code in the page

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

## Which versions are affected by CVE-2025-11184?


## How do I fix CVE-2025-11184?

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

## Is CVE-2025-11184 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-11184 and fix it if it is affected.

What it is: CVE-2025-11184 is a medium-severity cross-site scripting vulnerability in qwc-services qwc-registration-gui, published on 13 Oct 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-11184 exists.

Affected product: qwc-services qwc-registration-gui. 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-2025-11184/ (Markdown: https://insights.sbomify.com/CVE-2025-11184/index.md)
```

## Sources

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

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