Quick answers
- Is CVE-2026-51954 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-51954 being exploited in the wild.
- How severe is CVE-2026-51954?
- Informational severity, published 22 October 2026.
- Which products and versions are affected?
- Webasyst Framework 4.0.3 and before.
- Is there a fix for CVE-2026-51954?
- 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-51954 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-51954?
- Check whether you run Webasyst Framework 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 vulnerability stems from improper validation of the redirect_uri parameter in the OAuth authorization flow, allowing an attacker to craft a malicious OAuth authorization URL that redirects to an attacker-controlled site. This permits interception of authorization credentials and permanent API access tokens without requiring additional user interaction beyond normal OAuth approval. The flaw allows unauthenticated remote attackers to gain full unrestricted API access to a victim's account.
Affected products
- Webasyst Framework 4.0.3 and before
Timeline
- 2026-04-28: disclosed
- 2026-10-22: advisory