Temporary Login <= 1.0.0 - Authentication Bypass to Account Takeover
Strategic Overview
- Status
- Patched in 1.1.0
- Affected Plugin
- Temporary Login
- Affected Version
<= 1.0.0- CVSS
- 9.8Critical
- Weakness type
- CWE-288 · Authentication Bypass Using an Alternate Path or Channel
- CVE
CVE-2026-7567
At a glance
CVE-2026-7567 is a critical-severity Authentication Bypass Using an Alternate Path or Channel vulnerability in the Temporary Login WordPress plugin, affecting versions <= 1.0.0. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.1.0; sites on affected versions should update now. Disclosed April 2026, reported by TANG Cheuk Hei (siunam).
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-288: Authentication Bypass Using an Alternate Path or Channel
Temporary Login <= 1.0.0 carries this weakness at temp-login-token, and reaching it takes a caller who can reach the endpoint. Authentication bypass through an alternate path means the application has a second route to a protected action that skips the checks the primary route performs.
The protection on the main path becomes irrelevant, because the attacker simply uses the route that never asks. For Temporary Login the fix is 1.1.0: builds <= 1.0.0 are affected, anything from 1.1.0 onward is not.
Remediation
Update to version 1.1.0, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Temporary Login 1.1.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C