CVE-2026-110959 · Package
NO FIX YET · SEE WHAT TO DO
The Descope WordPress plugin before 1.2.0 does not check the authentication token it receives before creating a WordPress session, so any non-empty token is accepted. An unauthenticated attacker who knows an account's email address can get a logged-in session for that account, including an administrator.
first public Nov 12, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Sites running the Descope WordPress plugin before 1.2.0 that use it for login. The flaw is in the plugin's token handling during session creation, so any site with the vulnerable plugin active and reachable from the internet is exposed. Sites without the plugin, or running 1.2.0 or later, are not affected.
Not affected if plugin-not-installed, version-1.2.0-or-later
Who cares descope, self-hosted, wordpress
wp plugin get descope --field=version if WP-CLI is available.1.2.0.1.2.0 or later.The Descope WordPress plugin before 1.2.0 does not validate the authentication token it receives before creating a WordPress session, accepting any non-empty token, so an unauthenticated attacker can obtain a session for any existing account, including an administrator, by supplying that account's email address.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.