MyBlog index.php ID cross site scripting

Summaryinfo

A vulnerability has been found in MyBlog and classified as problematic. Affected by this issue is some unknown functionality of the file index.php. Performing a manipulation of the argument ID results in cross site scripting. This vulnerability is identified as CVE-2008-2962. The attack can be initiated remotely. Additionally, an exploit exists.

Detailsinfo

A vulnerability classified as problematic has been found in MyBlog (the affected version unknown). This affects an unknown part of the file index.php. The manipulation of the argument id with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as 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. This is going to have an impact on integrity. The summary by CVE is:

Multiple cross-site scripting (XSS) vulnerabilities in MyBlog allow remote attackers to inject arbitrary web script or HTML via the (1) s and (2) sort parameters to index.php, and the (3) id parameter to post.php.

The weakness was released 07/02/2008 (Website). It is possible to read the advisory at milw0rm.com. This vulnerability is uniquely identified as CVE-2008-2962 since 07/02/2008. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details and a public exploit are known. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK.

A public exploit has been developed by CWH Underground and been published even before and not after the advisory. The exploit is shared for download at exploit-db.com. It is declared as highly functional. The vulnerability was handled as a non-public zero-day exploit for at least 9 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 X-Force (43293), Exploit-DB (5913) and SecurityFocus (BID 29900†). Entries connected to this vulnerability are available at VDB-43012 and VDB-46636. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• MyBlog

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