Microsoft Visual Studio link following

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.0$0-$5k0.00

Summaryinfo

A vulnerability marked as problematic has been reported in Microsoft Visual Studio. Affected by this vulnerability is an unknown functionality. The manipulation leads to link following. This vulnerability is uniquely identified as CVE-2025-49739. The attack is possible to be carried out remotely. No exploit exists. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability was found in Microsoft Visual Studio (the affected version is unknown). It has been rated as problematic. This issue affects an unknown code. The manipulation with an unknown input leads to a link following vulnerability. Using CWE to declare the problem leads to CWE-59. The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource. Impacted is confidentiality, integrity, and availability.

The weakness was disclosed 07/08/2025 as confirmed security update guide (Website). The advisory is shared at msrc.microsoft.com. The identification of this vulnerability is CVE-2025-49739. 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. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/27/2025).

The vulnerability scanner Nessus provides a plugin with the ID 241959 (Security Updates for Microsoft Visual Studio Products (July 2025)), which helps to determine the existence of the flaw in a target environment.

Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (241959), EUVD (EUVD-2025-20538) and CERT Bund (WID-SEC-2025-1485). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Fedora Linux
  • Ubuntu Linux
  • Oracle Linux
  • Gentoo Linux
  • SUSE openSUSE
  • Red Hat OpenShift
  • Microsoft Visual Studio 2015
  • Microsoft Visual Studio 2017
  • Microsoft Visual Studio Code
  • Microsoft Visual Studio 2019
  • Microsoft Visual Studio 2022
  • Open Source git
  • cPanel cPanel/WHM
  • Open Source Gitea

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.9
VulDB Meta Temp Score: 6.1

VulDB Base Score: 5.0
VulDB Temp Score: 4.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

Vendor Base Score (Microsoft): 8.8
Vendor Vector (Microsoft): 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Link following
CWE: CWE-59
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Unproven

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 241959
Nessus Name: Security Updates for Microsoft Visual Studio Products (July 2025)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

Reaction Time: 🔒
0-Day Time: 🔒
Exposure Time: 🔒

Timelineinfo

07/08/2025 VulDB entry created
07/08/2025 +0 days Advisory disclosed
07/08/2025 +0 days Countermeasure disclosed
08/27/2025 +49 days VulDB entry last update

Sourcesinfo

Vendor: microsoft.com

Advisory: msrc.microsoft.com
Status: Confirmed

CVE: CVE-2025-49739 (🔒)
GCVE (CVE): GCVE-0-2025-49739
GCVE (VulDB): GCVE-100-315557
EUVD: 🔒
CERT Bund: WID-SEC-2025-1485 - Microsoft Developer Tools und git: Mehrere Schwachstellen

Entryinfo

Created: 07/08/2025 19:58
Updated: 08/27/2025 01:24
Changes: 07/08/2025 19:58 (7), 07/08/2025 19:59 (23), 07/08/2025 20:02 (38), 07/09/2025 08:55 (1), 07/12/2025 08:17 (2), 08/27/2025 01:24 (7)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!