CVE-2022-23961
Reflected XSS in Thruk Monitoring Interface
Publication date: 2026-05-08
Last updated on: 2026-05-08
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| thruk_monitoring | thruk_monitoring | to 2.46.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify how the reflected XSS vulnerability in Thruk Monitoring affects compliance with common standards and regulations such as GDPR or HIPAA.
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to upgrade Thruk Monitoring to version 2.46.3 or later, where the vulnerability has been fixed.
Additionally, ensure proper input validation and output encoding are implemented to prevent reflected XSS attacks.
Can you explain this vulnerability to me?
CVE-2022-23961 is a reflected Cross-Site Scripting (XSS) vulnerability in Thruk Monitoring versions prior to v2.46.3. It occurs in the login form's "login" field, where user input is reflected in error messages without proper encoding or filtering.
This allows unauthenticated remote attackers to inject and execute malicious JavaScript payloads by submitting crafted input to the login field.
How can this vulnerability impact me? :
This vulnerability can be exploited by attackers to execute malicious scripts in the context of users accessing the Thruk Monitoring interface.
Such attacks can lead to session hijacking, theft of sensitive information, or performing actions on behalf of the user without their consent.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the login form's "login" field for reflected Cross-Site Scripting (XSS) issues. Specifically, you can submit crafted input containing JavaScript payloads in the login field and observe if the input is reflected unencoded in the response, such as in error messages.
A simple detection method is to use tools like curl or a web browser to submit payloads and check the response for reflected scripts.
- Example curl command to test the login field for reflected XSS: curl -X POST -d "login=<script>alert(1)</script>" https://your-thruk-instance/login
- Alternatively, use a web proxy or browser developer tools to submit the payload and inspect the response for unencoded reflection of the input.