CVE-2026-7567 CRITICAL

CVE-2026-7567: Temporary Login <= 1.0.0 - Authentication Bypass to Account Takeover

Vendor Elemntor
Product Temporary Login
Weakness CWE-288
Published May 1, 2026
Last update May 1, 2026

CVSS base score

9.8/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Confidentiality High
Integrity High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

What the vulnerability does

01Description

The Temporary Login plugin for WordPress is vulnerable to Authentication Bypass in versions up to and including 1.0.0. This is due to improper input validation in the maybe_login_temporary_user() function, which fails to verify that the 'temp-login-token' GET parameter is a scalar string before processing it. When the parameter is supplied as an array, PHP's empty() check is bypassed and sanitize_key() returns an empty string, which is then passed as the meta_value to get_users(). WordPress ignores an empty meta_value and returns all users matching the meta_key '_temporary_login_token', allowing authentication without a valid token. This makes it possible for unauthenticated attackers to authenticate as any active temporary login user by sending a single crafted GET request.

Explanation of Vulnerability in Simple Terms

02Summary

Elementor's Temporary Login plugin version 1.0.0 and earlier contains an authentication bypass vulnerability. An attacker can gain unauthorized access to user accounts without valid credentials. The vulnerability affects authentication mechanisms in the plugin, allowing complete compromise of affected sites. Immediate patching is required.

What an attacker can do

03Attacker Capabilities

Gain unauthorized access to user accounts and perform actions as any user without knowing their password.

Potential impact on your site

04Site Impact

Attackers can log in as any user, including administrators, and take full control of your site.

Conditions required to exploit

05Prerequisites

Network access only; no authentication or user interaction required.

Key dates

06Disclosure timeline

May 1, 2026 CVE published
May 1, 2026 Record updated