Pragyan CMS 2.6.4 index.php fileget sql injection

Summaryinfo

A vulnerability described as critical has been identified in Pragyan CMS 2.6.4. Impacted is an unknown function of the file index.php. The manipulation of the argument fileget results in sql injection. This vulnerability is identified as CVE-2009-1480. The attack can be executed remotely. Additionally, an exploit exists.

Detailsinfo

A vulnerability was found in Pragyan CMS 2.6.4 (Content Management System). It has been classified as critical. Affected is an unknown code block of the file index.php. The manipulation of the argument fileget with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

SQL injection vulnerability in index.php Pragyan CMS 2.6.4 allows remote attackers to execute arbitrary SQL commands via the fileget parameter in a view action and other unspecified vectors.

The weakness was released 04/29/2009 (Website). The advisory is shared for download at securityfocus.com. This vulnerability is traded as CVE-2009-1480 since 04/29/2009. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details and a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1505.

A public exploit has been developed by Salvatore Fresta and been published even before and not after the advisory. The exploit is shared for download 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 5 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 databases at Exploit-DB (8533) and SecurityFocus (BID 34707†). VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

• Content Management System

Vendor

• Pragyan

Name

• CMS

Version

• 2.6.4

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion