CVE-2023-54341
Reflected XSS in Webgrind 1.1 Allows Script Injection
Publication date: 2026-01-13
Last updated on: 2026-02-03
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| jokkedk | webgrind | to 1.1 (inc) |
| webgrind_project | webgrind | to 1.1 (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
Can you explain this vulnerability to me?
CVE-2023-54341 is a reflected Cross-Site Scripting (XSS) vulnerability in Webgrind version 1.1 and earlier. It occurs because the application does not properly encode user input passed via the "file" parameter in the index.php file. This allows unauthenticated attackers to craft malicious URLs that inject and execute arbitrary JavaScript code in the browsers of users who click those URLs. [1, 2]
How can this vulnerability impact me? :
This vulnerability can allow attackers to execute arbitrary JavaScript in the victim's browser, potentially leading to session hijacking, defacement of the web interface, or other malicious actions that compromise user interaction with the application. Since it requires user interaction (clicking a malicious URL), the impact is medium severity but can still lead to significant security issues. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'file' parameter in the /index.php endpoint of Webgrind 1.1 or earlier for reflected Cross-Site Scripting (XSS). You can craft URLs that inject JavaScript code into the 'file' parameter and observe if the script is executed or reflected in the HTTP response. For example, you can use curl or a browser to send requests like: curl -i 'http://<target>/index.php?file=<script>alert(1)</script>' and check if the script tag is reflected unencoded in the response. Additionally, monitoring HTTP requests for suspicious or malformed 'file' parameter values may help detect exploitation attempts. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating Webgrind to a version later than 1.1 where this vulnerability is fixed. If an update is not immediately possible, implement input validation and proper encoding on the 'file' parameter to prevent script injection. Additionally, consider applying web application firewall (WAF) rules to block requests containing suspicious script tags or JavaScript code in the 'file' parameter. Educate users to avoid clicking on suspicious URLs that may exploit this vulnerability. [1, 2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not contain information regarding the impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.