Menu

Star on GitHub · 3.2k

CVE-2006-4975

2.6 · LOW

Yahoo!

Published Sep 25, 2006yahooEPSS 1.22%

Overview

CVE-2006-4975 is a low-severity vulnerability affecting yahoo messenger. It was published on September 25, 2006 and has a CVSS 2.0 base score of 2.6 (LOW).

This vulnerability has a CVSS 2.0 base score of 2.6, rated LOW. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

Yahoo! Messenger for WAP permits saving messages that contain JavaScript, which allows user-assisted remote attackers to inject arbitrary web script or HTML via a URL at the online service.

Remediation

Check the references section for vendor advisories and patches from yahoo. Update messenger to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2006-4975?

CVE-2006-4975 is a low-severity vulnerability affecting yahoo messenger. It was published on September 25, 2006 and has a CVSS 2.0 base score of 2.6 (LOW).

How severe is CVE-2006-4975?

This vulnerability has a CVSS 2.0 base score of 2.6, rated LOW. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2006-4975?

Check the references section for vendor advisories and patches from yahoo. Update messenger to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2006-4975?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2006-4975 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related LOW CVEs from 2006

View all