Uwix Com Digifolio 1.52 index.php ID sql injection

Summaryinfo

A vulnerability classified as critical has been found in Uwix Com Digifolio 1.52. The impacted element is an unknown function of the file index.php. This manipulation of the argument ID causes sql injection. This vulnerability is registered as CVE-2009-3193. Remote exploitation of the attack is possible. Furthermore, an exploit is available.

Detailsinfo

A vulnerability has been found in Uwix Com Digifolio 1.52 and classified as critical. Affected by this vulnerability is some unknown processing of the file index.php. The manipulation of the argument id 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:

SQL injection vulnerability in the DigiFolio (com_digifolio) component 1.52 for Joomla! allows remote attackers to execute arbitrary SQL commands via the id parameter in a project action to index.php.

The weakness was published 09/15/2009 (Website). It is possible to read the advisory at milw0rm.com. This vulnerability is known as CVE-2009-3193 since 09/15/2009. 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.

A public exploit has been developed by v3n0m and been published before and not just after the advisory. It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 19 days. During that time the estimated underground price was around $0-$5k. 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 (9534). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• Uwix

Name

• Com Digifolio

Version

• 1.52

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