CVE-2026-110959VulnerabilityPublished 12 Nov 2026

The Descope WordPress plugin before 1.2.0 does not validate the authentication token it receives before creating a

Source GCVE Database

Compare

Authoritative record:CVE-2026-110959· High

Not known to be exploited : upgrade to 1.2.0 soon.

Data as of 12 Nov 2026, 07:05 UTC

Severity

High

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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-ff68-vpqw-wj7c

What to do

Upgrade Descope (WordPress plugin) to 1.2.0.

Affected software

Product	Affected	Fixed in
Descope	Affected <1.2.0	Fixed in 1.2.0

AI-suggested

Upgrade the Descope WordPress plugin to version 1.2.0 or later, where this vulnerability is fixed. Since the vulnerability affects versions before 1.2.0, updating to the fixed version is the recommended remediation. No vendor advisory or patch links were provided, but the version boundary indicates a fix in 1.2.0.

Description

The Descope WordPress plugin versions before 1.2.0 contain a vulnerability where the plugin does not validate authentication tokens before creating WordPress sessions. This allows an unauthenticated attacker to obtain a session for any existing user account, including administrators, by supplying the target account's email address.

Impact

An attacker can gain unauthorized access to any user account on the affected WordPress site, including administrator accounts, without valid authentication credentials. This can lead to full compromise of the site, unauthorized content modification, data exposure, and potential further exploitation.

Summary

The Descope WordPress plugin prior to version 1.2.0 fails to validate the authentication token it receives before creating a WordPress session. Instead, it accepts any non-empty token, enabling an unauthenticated attacker to impersonate any user by providing that user's email address. This flaw effectively bypasses authentication controls and grants unauthorized access to user sessions, including those with administrative privileges.

References

Community reviews

Loading reviews…