Plugins · temporary-login · data as of 2026-11-04
Is Temporary Login safe? Known vulnerabilities and latest version
- Latest version
- 1.3.0
- Last updated
- 2024-11-26
- Active installs
- 30,000+
- Known issues on record
- 1
- Unpatched in latest
- 0
- Tested up to WP
- 6.7.11 · PHP 7.4+
Create a secure, temporary URL for easy access to your WP admin. — by Elementor
What to do
- Update to the latest version (1.3.0). Anything older than 1.1.0 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get temporary-login --field=version shows what you run; wp plugin update temporary-login updates it.
Check your version
Known vulnerabilities
1 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
critical 9.8 CVE-2026-7567 · published 2026-05-01
Authentication bypass in Temporary Login (1.0.0 and older)
- Affected
- 1.0.0 and older
- Fixed in
- 1.1.0 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
Recent activity
- 2024-11-26 — latest release on wordpress.org (1.3.0).
- 2026-05-01 — Authentication bypass disclosed (CVE-2026-7567), fixed in 1.1.0.
Get an email when Temporary Login has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Temporary Login (temporary-login) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
- Published this week
- Unpatched in the latest version
- By type of vulnerability
- Plugins by Elementor (6 tracked)
Types found in this plugin: Authentication bypass (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/temporary-login (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/temporary-login"><img src="https://laskyr.com/plugins/temporary-login/badge.svg" alt="Temporary Login vulnerability status"></a>