Wdmtech vAccount 2.0.2 GET Request vid sql injection

Summaryinfo

A vulnerability labeled as critical has been found in Wdmtech vAccount 2.0.2. This vulnerability affects unknown code of the component GET Request Handler. Such manipulation of the argument vid leads to sql injection. This vulnerability is uniquely identified as CVE-2019-25756. The attack can be launched remotely. Moreover, an exploit is present.

Detailsinfo

A vulnerability was found in Wdmtech vAccount 2.0.2 and classified as critical. Affected by this issue is an unknown part of the component GET Request Handler. The manipulation of the argument vid with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. CVE summarizes:

Joomla! Component vAccount 2.0.2 contains an SQL injection vulnerability that allows unauthenticated attackers to execute arbitrary SQL queries by injecting malicious code through the vid parameter. Attackers can send GET requests to the vaccount-dashboard/expense endpoint with crafted SQL payloads in the vid parameter to extract sensitive database information including version and database names.

The weakness was disclosed by Ihsan Sencan as 46226. The advisory is shared for download at exploit-db.com. This vulnerability is handled as CVE-2019-25756 since 06/19/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details as well as a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1505.

The exploit is available 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 (46226). Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• Wdmtech

Name

• vAccount

Version

• 2.0.2

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