Impact
A flaw in Element Call versions 0.5.17 through 0.19.3 causes analytics data to include the full URL of a user's visited page, which may contain an encryption password. The data is sent to a PostHog server when analytics are enabled, leaking sensitive call information that could allow an attacker who can read the analytics stream to compromise the confidentiality of the encrypted media. This is an information‑disclosure weakness (CWE‑200).
Affected Systems
The issue is limited to standalone Element Call installations, such as https://call.element.io, that use the posthog key or the posthogApiHost and posthogApiKey URL parameters. Embedded Element Call packages used within Element Web, Desktop, and mobile applications are not affected because they transmit encryption keys through the Matrix protocol rather than within URLs. Affected versions range from 0.5.17 to 0.19.3; the vulnerability is patched in 0.19.4.
Risk and Exploitability
The CVSS score of 8.6 marks this as a high‑severity vulnerability, and while EPSS is not available, the lack of a KEV listing does not reduce the potential impact. Exploitation requires that analytics be enabled and the relevant key present; an attacker can influence a user’s URL or rely on an administrator’s misconfiguration to cause sensitive data to be sent to the analytics server. The primary attack vector is via the analytics configuration, either through user‑controlled links or server‑side misconfiguration, and the exploitation would result in disclosure of call encryption passwords.
OpenCVE Enrichment
Github GHSA