jokkedk Webgrind 1.1 index.php File cross site scripting

Summaryinfo

A vulnerability categorized as problematic has been discovered in jokkedk Webgrind 1.1. This impacts an unknown function of the file index.php. Executing a manipulation of the argument File can lead to cross site scripting. This vulnerability is registered as CVE-2023-54341. It is possible to launch the attack remotely. Furthermore, an exploit is available.

Detailsinfo

A vulnerability classified as problematic was found in jokkedk Webgrind 1.1. This vulnerability affects an unknown functionality of the file index.php. The manipulation of the argument file with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect integrity. CVE summarizes:

Webgrind 1.1 and before contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject malicious scripts via the file parameter in index.php. The application does not sufficiently encode user-controlled inputs, allowing attackers to execute arbitrary JavaScript in victim's browsers by crafting malicious URLs.

The weakness was published by Rafael Pedrero as 51074. The advisory is shared for download at exploit-db.com. This vulnerability was named CVE-2023-54341 since 01/10/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. Technical details and also a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1059.007.

It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:index.php it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Exploit-DB (51074). Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• jokkedk

Name

• Webgrind

Version

• 1.1

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion