# CVE-2022-23961: Cross-site scripting in n/a

> Unauthenticated remote attackers can execute arbitrary scripts in the context of monitoring interface users via reflected XSS in the login field.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 May 2026
- **Updated:** 8 May 2026
- **Also known as:** GHSA-hqhv-x7gw-gg62

## What is CVE-2022-23961?

CVE-2022-23961 is a medium-severity cross-site scripting vulnerability in n/a, published on 8 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

In Thruk Monitoring through 2.46.3, the login field of the login form is vulnerable to reflected XSS. This vulnerability can be exploited by unauthenticated remote attackers to target users of the monitoring interface.

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

## Which versions are affected by CVE-2022-23961?


## How do I fix CVE-2022-23961?

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

## Is CVE-2022-23961 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-23961 and fix it if it is affected.

What it is: CVE-2022-23961 is a medium-severity cross-site scripting vulnerability in n/a, published on 8 May 2026. An attacker can exploit it over the internet without logging in, 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-2022-23961 exists.

Affected product: n/a. 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-2022-23961/ (Markdown: https://insights.sbomify.com/CVE-2022-23961/index.md)
```

## Sources

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

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