VDB-294882 · CVE-2024-36556 · EUVD-2025-5057

Forever KidsWatch Call Me KW50/KidsWatch Call Me 2 KW60 hard-coded password

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.
4.6	$0-$5k	0.00

Summaryinfo

A vulnerability classified as problematic was found in Forever KidsWatch Call Me KW50 and KidsWatch Call Me 2 KW60. Impacted is an unknown function. The manipulation results in hard-coded password. This vulnerability is reported as CVE-2024-36556. No exploit exists.

Detailsinfo

A vulnerability was found in Forever KidsWatch Call Me KW50 and KidsWatch Call Me 2 KW60 (version unknown). It has been classified as problematic. Affected is an unknown function. The manipulation with an unknown input leads to a hard-coded password vulnerability. CWE is classifying the issue as CWE-259. The product contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components. The impact remains unknown. CVE summarizes:

Forever KidsWatch Call Me KW50 R36_YDR_A3PW_GM7S_V1.0_2019_07_15_16.19.24_cob_h, and Forever KidsWatch Call Me 2 KW60 R36CW_YDE_S4_A29_2_V1.0_2023.05.24_22.49.44_cob_b have a Hardcoded password vulnerability.

This vulnerability is traded as CVE-2024-36556 since 05/30/2024. The exploitability is told to be difficult. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1078.001 by the MITRE ATT&CK project.

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 vulnerability database at EUVD (EUVD-2025-5057). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

Forever

Name

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.6
VulDB Meta Temp Score: 4.6

VulDB Base Score: 4.6
VulDB Temp Score: 4.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AV	AC	Au	C	I	A
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳

Vector	Complexity	Authentication	Confidentiality	Integrity	Availability
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock

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

Exploitinginfo

Class: Hard-coded password
CWE: CWE-259 / CWE-255
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Day	Unlock	Unlock	Unlock	Unlock
Today	Unlock	Unlock	Unlock	Unlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

05/30/2024 🔍
02/06/2025 +252 days 🔍
02/06/2025 +0 days 🔍
06/01/2025 +115 days 🔍

Sourcesinfo

Status: Not defined

CVE: CVE-2024-36556 (🔍)
GCVE (CVE): GCVE-0-2024-36556
GCVE (VulDB): GCVE-100-294882
EUVD: 🔍

Entryinfo

Created: 02/06/2025 20:31
Updated: 06/01/2025 07:58
Changes: 02/06/2025 20:31 (49), 06/01/2025 07:58 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.