CVE-2026-110959: Descope (WordPress plugin) · Improper Authentication
Affects Descope (WordPress plugin)Source CVE Database V5
Not known to be exploited : upgrade to 1.2.0 soon.
Data as of 12 Nov 2026, 06:32 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 1.2.0
Exploitation evidence
Disclosed: evidence found.
CVE published 12 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 11 Nov 2026.
What to do
Upgrade Descope (WordPress plugin) to 1.2.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Descope | Affected
| Fixed in
|
AI-suggested
Upgrade the Descope WordPress plugin to version 1.2.0 or later, where this authentication validation flaw has been fixed. No other mitigation is required once the plugin is updated.
Description
The Descope WordPress plugin versions before 1.2.0 contain an improper authentication vulnerability. The plugin does not validate authentication tokens before creating WordPress sessions, accepting any non-empty token. This flaw allows an unauthenticated attacker to obtain a session for any existing user account, including administrators, by supplying the target account's email address.