FKIE_CVE-2026-16624

Vulnerability from fkie_nvd - Published: 2026-07-22 19:16 - Updated: 2026-07-22 19:16
Severity
Summary
Cal.com OSS ships lacks authorization on webhook teamId creation, allowing any authenticated user to create a webhook on any team via unvalidated teamId injection, then steal booking data, including fields like organizer/attendee emails and custom responses, and conditionally video-call passwords, by triggering webhook delivery.
Impacted products
Vendor Product Version

{
  "affected": [
    {
      "affectedData": [
        {
          "product": "Cal.diy",
          "vendor": "Cal.com",
          "versions": [
            {
              "lessThan": "6.2.0",
              "status": "affected",
              "version": "0",
              "versionType": "custom"
            }
          ]
        }
      ],
      "source": "cret@cert.org"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "Cal.com OSS ships lacks authorization on webhook teamId creation, allowing any authenticated user to create a webhook on any team via unvalidated teamId injection, then steal booking data, including fields like organizer/attendee emails and custom responses, and conditionally video-call passwords, by triggering webhook delivery."
    }
  ],
  "id": "CVE-2026-16624",
  "lastModified": "2026-07-22T19:16:58.273",
  "metrics": {},
  "published": "2026-07-22T19:16:58.273",
  "references": [
    {
      "source": "cret@cert.org",
      "url": "https://github.com/calcom/cal.diy/security/advisories/GHSA-4fwh-xxpv-xfm6"
    },
    {
      "source": "cret@cert.org",
      "url": "https://vokecyber.com/research/calcom-cross-tenant-webhook-plant"
    }
  ],
  "sourceIdentifier": "cret@cert.org",
  "vulnStatus": "Received"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

Loading…