The OneLogin SAML SSO WordPress plugin before 3.7.1 does not validate a user-supplied parameter before using it to
Source GCVE Database
Not known to be exploited : upgrade to 3.7.1 when convenient.
Data as of 18 Nov 2026, 08:07 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 3.7.1
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade OneLogin SAML SSO (WordPress plugin) to 3.7.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OneLogin SAML SSO | Affected
| Fixed in
|
AI-suggested
Upgrade the OneLogin SAML SSO WordPress plugin to version 3.7.1 or later, where this validation issue has been fixed. No other mitigation steps are indicated.
Description
The OneLogin SAML SSO WordPress plugin versions before 3.7.1 contain a vulnerability where a user-supplied parameter is not validated before being used to redirect an authenticated user. This flaw allows unauthenticated attackers to craft links that redirect logged-in users to arbitrary external domains, potentially facilitating phishing attacks.