Severity by source
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Network-accessible unauthenticated socket endpoint; scope changes as server queries other internal systems; only low confidentiality impact due to iCal parsing requirement for exfiltration.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
3DescriptionCVE.org
MagicMirror² is an open source modular smart mirror platform. Prior to 2.37.0, the ADD_CALENDAR handler in defaultmodules/calendar/node_helper.js accepts an attacker-controlled URL, authentication data, and selfSignedCert setting through the unauthenticated Socket.IO namespace /calendar. The handler passes these fields to CalendarFetcher, causing a server-side request without SSRF validation and optionally disabling TLS verification. When the response is valid iCal, CALENDAR_EVENTS returns parsed event data to the attacker, allowing internal-service response data to be exfiltrated; other responses still provide a blind request and timing primitive. This issue is fixed in version 2.37.0.
AnalysisAI
Server-side request forgery in MagicMirror² versions prior to 2.37.0 allows unauthenticated remote attackers to make the mirror server issue arbitrary outbound HTTP requests to attacker-controlled URLs, including to internal network services. The vulnerability stems from the ADD_CALENDAR handler on the unauthenticated Socket.IO /calendar namespace accepting a fully attacker-controlled URL, authentication headers, and a TLS-bypass flag with no SSRF validation. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | The attacker must be able to reach the MagicMirror² HTTP port (default 8080) over the network - in default home installations this means LAN access, though misconfigured port forwarding could expose it externally. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 4.0 score of 6.3 with vector AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N reflects network-accessible, unauthenticated exploitation with low confidentiality impact across both the vulnerable component and reachable subsequent systems. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Upgrade MagicMirror² to version 2.37.0, which is the vendor-confirmed fixed release (GitHub tag v2.37.0, commit 58c2a5e675a7d367b64d72e1d35680d202ff5c9f via PR #4169). … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
More in Magicmirror
View allUnauthenticated Server-Side Request Forgery in MagicMirror² versions prior to 2.37.0 allows any network-reachable attack
Secret environment variable disclosure in MagicMirror² before 2.37.0 allows adjacent network attackers to recover live S
Socket.IO namespace access control bypass in MagicMirror² prior to v2.37.0 allows unauthenticated adjacent-network clien
Same weakness CWE-918 – Server-Side Request Forgery (SSRF)
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-61071
GHSA-w6x9-28jw-hq7j