TomatoCMS up to 2.0.6 index.php address cross site scripting

Summaryinfo

A vulnerability has been found in TomatoCMS up to 2.0.6 and classified as problematic. The affected element is an unknown function of the file index.php. The manipulation of the argument address leads to cross site scripting. This vulnerability is traded as CVE-2010-1515. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in TomatoCMS up to 2.0.6 and classified as problematic. This issue affects an unknown part of the file index.php. The manipulation of the argument address with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to 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. Impacted is integrity. The summary by CVE is:

Multiple cross-site scripting (XSS) vulnerabilities in index.php in TomatoCMS 2.0.6 and earlier allow remote attackers to inject arbitrary web script or HTML via the (1) keyword or (2) article-id parameter in conjunction with a /admin/news/article/list PATH_INFO; the (3) keyword parameter in conjunction with a /admin/multimedia/set/list PATH_INFO; the (4) keyword or (5) fileId parameter in conjunction with a /admin/multimedia/file/list PATH_INFO; or the (6) name, (7) email, or (8) address parameter in conjunction with a /admin/ad/client/list PATH_INFO.

The weakness was shared 06/15/2010 with Secunia Research (Website). The advisory is shared at securityfocus.com. The identification of this vulnerability is CVE-2010-1515 since 04/26/2010. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.

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 SecurityFocus (BID 40544†) and Secunia (SA39680†). The entries VDB-53627, VDB-53626 and VDB-53608 are related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• TomatoCMS

Version

• 2.0.0
• 2.0.1
• 2.0.2
• 2.0.3
• 2.0.3.1430
• 2.0.3.1622
• 2.0.4
• 2.0.5
• 2.0.6

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