Quick answers
- Is CVE-2026-102245 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-102245 being exploited in the wild.
- How severe is CVE-2026-102245?
- High severity, with a CVSS score of 7.3, published 29 September 2026.
- Which products and versions are affected?
- MODSetter SurfSense up to 2.0.3.
- Is there a fix for CVE-2026-102245?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-102245 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-102245?
- Check whether you run MODSetter SurfSense at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The POST /api/v1/webhooks/circleback/{workspace_id} endpoint lacks authentication and signature verification, accepting arbitrary Circleback meeting payloads. Workspace IDs are sequential integers, making enumeration trivial. Injected documents are indexed into the knowledge base and can overwrite existing meetings, with no verification that the caller is a legitimate Circleback connector or that the workspace owner authorized the webhook.
Affected products
- MODSetter SurfSense up to 2.0.3
Timeline
- 2026-09-29: disclosed
- 2026-08-17: exploited: Proof of concept published on GitHub