jokkedk Webgrind 1.1 index.php dataFile os command injection

Summaryinfo

A vulnerability was found in jokkedk Webgrind 1.1. It has been classified as critical. The affected element is an unknown function of the file index.php. This manipulation of the argument dataFile causes os command injection. This vulnerability is tracked as CVE-2023-54339. The attack is possible to be carried out remotely. Moreover, an exploit is present.

Detailsinfo

A vulnerability was found in jokkedk Webgrind 1.1. It has been declared as critical. Affected by this vulnerability is an unknown code block of the file index.php. The manipulation of the argument dataFile with an unknown input leads to a os command injection vulnerability. The CWE definition for the vulnerability is CWE-78. The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Webgrind 1.1 contains a remote command execution vulnerability that allows unauthenticated attackers to inject OS commands via the dataFile parameter in index.php. Attackers can execute arbitrary system commands by manipulating the dataFile parameter, such as using payload '0%27%26calc.exe%26%27' to execute commands on the target system.

The weakness was disclosed by Rafael Pedrero as 51074. The advisory is shared at exploit-db.com. This vulnerability is known as CVE-2023-54339 since 01/10/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1202 for this issue.

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). Several companies clearly confirm that VulDB is the primary source for best 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

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion