VulnerabilityPublished 29 Apr 2024Updated 4 Nov 2024

CVE-2024-31747: An issue in Yealink VP59 Microsoft Teams Phone firmware 91.15.0.118 (fixed in 122.15.0.142) allows a

Source CVE Database V5

Not known to be exploited · CVSS 2.1 Low · fixed in 122.15.0.142 : update affected systems when convenient.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score

2.1Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 122.15.0.142

CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L

Attack Vector: Physical
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Apr 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Upgrade all Yealink VP59 Microsoft Teams Phones to firmware version 122.15.0.142 or later, which contains the fix for this vulnerability.
Implement strict physical security controls to prevent unauthorized physical access to VoIP devices, including secure office environments and locked rooms.
Disable or restrict access to the Walkie Talkie menu option if it is not required for business operations.
Regularly audit device configurations and access logs to detect any unauthorized usage.
Educate staff about the risks of physical device tampering and encourage reporting of suspicious activity.
Consider network segmentation for VoIP devices to limit potential lateral movement if a device is compromised.
Maintain an up-to-date inventory of all VoIP devices and their firmware versions to ensure timely patching.

Description

An issue in Yealink VP59 Microsoft Teams Phone firmware 91.15.0.118 (fixed in 122.15.0.142) allows a physically proximate attacker to disable the phone lock via the Walkie Talkie menu option.

Impact

The primary impact of this vulnerability is on the availability and physical security of the Yealink VP59 Teams Phone devices. An attacker with physical access can disable the phone lock, potentially allowing unauthorized use of the device, which could lead to misuse of telephony services or unauthorized calls. Although this does not directly compromise sensitive data or system integrity, it could facilitate social engineering or other attacks by impersonating legitimate users. Organizations relying heavily on these devices for communication, especially in secure or sensitive environments, may face operational disruptions or reputational risks. The low CVSS score indicates limited risk, but environments with lax physical security controls are more vulnerable. Since no exploits are known in the wild, the immediate threat is low but should not be ignored.

References

medium.com/%40deepsahu1/yealink-vp59-microsoft-teams-phone-lock-bypass-b7fee9dd9c8c (opens in a new tab)

Community reviews

Loading reviews…