Webiness Inventory 2.3 WsModelGrid.php order sql injection

Summaryinfo

A vulnerability classified as critical has been found in Webiness Inventory 2.3. Impacted is an unknown function of the file WsModelGrid.php. This manipulation of the argument order causes sql injection. This vulnerability appears as CVE-2018-25188. The attack may be initiated remotely. In addition, an exploit is available.

Detailsinfo

A vulnerability classified as critical was found in Webiness Inventory 2.3. Affected by this vulnerability is some unknown processing of the file WsModelGrid.php. The manipulation of the argument order with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL 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:

Webiness Inventory 2.3 contains an SQL injection vulnerability that allows unauthenticated attackers to execute arbitrary SQL queries by injecting malicious code through the order parameter. Attackers can send POST requests to the WsModelGrid.php endpoint with crafted SQL payloads to extract sensitive database information including usernames, databases, and version details.

The weakness was presented by Ihsan Sencan as 45843. The advisory is shared at exploit-db.com. This vulnerability is known as CVE-2018-25188 since 03/06/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 T1505 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:WsModelGrid.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 databases at Exploit-DB (45843) and EUVD (EUVD-2018-21641). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Webiness Inventory

Version

• 2.3

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion