Wdmtech vReview 1.9.11 editReview Task Endpoint cmId sql injection

Summaryinfo

A vulnerability identified as critical has been detected in Wdmtech vReview 1.9.11. This affects an unknown part of the component editReview Task Endpoint. This manipulation of the argument cmId causes sql injection. This vulnerability is handled as CVE-2019-25755. The attack can be initiated remotely. Additionally, an exploit exists.

Detailsinfo

A vulnerability has been found in Wdmtech vReview 1.9.11 and classified as critical. Affected by this vulnerability is some unknown functionality of the component editReview Task Endpoint. The manipulation of the argument cmId 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:

Joomla Component vReview 1.9.11 contains an SQL injection vulnerability that allows unauthenticated attackers to execute arbitrary SQL queries by injecting malicious code through the cmId parameter. Attackers can send POST requests to the editReview task endpoint with URL-encoded SQL UNION statements in the cmId parameter to extract database information including usernames, passwords, and database versions.

The weakness was released by Ihsan Sencan as 46227. It is possible to read the advisory at exploit-db.com. This vulnerability is known as CVE-2019-25755 since 06/19/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. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.

It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept.

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 (46227). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• Wdmtech

Name

• vReview

Version

• 1.9.11

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion