The Vexa webhook feature accepts an arbitrary URL to post meeting‑completion data. Because no validation is performed, an attacker who is authenticated can configure that URL to point to internal services, cloud metadata endpoints, or localhost resources. By forcing the application to contact those targets, the attacker can gather internal network information, extract credentials from cloud metadata services, or interact with database or admin interfaces. This SSRF flaw allows the attacker to potentially read or manipulate data inside the environment, affecting confidentiality and integrity of the internal infrastructure. The flaw is represented by CWE‑918.

Any instance of the Vexa HTTP API running versions earlier than 0.10.0‑260419‑1910 is vulnerable. The affected product is Vexa‑AI Vexa, a self‑hosted meeting bot and transcription API. Authenticated users controlling the webhook configuration are the attack surface.

The CVSS score of 5.8 indicates a moderate severity. The EPSS score is not available, so exploitation probability is unknown. It is not listed in the CISA KEV catalog. Because the flaw requires only an authenticated user and affecting an internal request, an attacker with sufficient access can exploit it without needing complex setups. The most straightforward attack vector is an authenticated user setting a webhook URL that points to an internal service or cloud metadata endpoint.