Temporary Login
Approved changes feed: RSS · Atom
cpe:2.3:a:elemntor:temporary_login:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Elemntor (cc4af95b-e1c9-5b8a-bdfb-177771c72ff1) |
|---|---|
| Product | Temporary Login (237d8792-4eab-5981-9a23-552a0005cf76) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-7567 |
vulnerable | 2026-06-08 08:08:57.412671 |
Temporary Login <= 1.0.0 - Authentication Bypass to Account Takeover
CRITICAL (9.8)
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.
Published: 2026-05-01T09:26:06.824Z
Updated: 2026-05-01T14:27:42.580Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.