TGS CMS up to 0.3.2 login.php previous_page cross site scripting

Summaryinfo

A vulnerability marked as problematic has been reported in TGS CMS up to 0.3.2. This affects an unknown function of the file login.php. This manipulation of the argument previous_page causes cross site scripting. This vulnerability is registered as CVE-2009-2928. Remote exploitation of the attack is possible. Furthermore, an exploit is available.

Detailsinfo

A vulnerability has been found in TGS CMS up to 0.3.2 (Content Management System) and classified as problematic. Affected by this vulnerability is an unknown code of the file login.php. The manipulation of the argument previous_page with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. As an impact it is known to affect integrity. The summary by CVE is:

Cross-site scripting (XSS) vulnerability in login.php in TGS Content Management 0.x allows remote attackers to inject arbitrary web script or HTML via the previous_page parameter, a different vector than CVE-2008-6839.

The weakness was published 08/21/2009 (Website). The advisory is shared at milw0rm.com. This vulnerability is known as CVE-2009-2928 since 08/21/2009. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details and also a public exploit are known. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.

A public exploit has been developed by []ViZiOn and been published even before and not after the advisory. It is possible to download the exploit at exploit-db.com. It is declared as highly functional. The vulnerability was handled as a non-public zero-day exploit for at least 8 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:login.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 X-Force (52481), Exploit-DB (9434) and SecurityFocus (BID 36401†). Similar entry is available at VDB-49586. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Content Management System

Vendor

• TGS

Name

• CMS

Version

• 0.1.6
• 0.1.7
• 0.2.0
• 0.2.5
• 0.3.0
• 0.3.2

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion