WordPress security by component
Temporary Login Without Password
Plugin description
Temporary Login Without Password creates temporary login links that provide passwordless WordPress access.
Temporary Login Without Password (temporary-login-without-password) is a WordPress plugin with 3 published CVE records in this archive. The latest tracked vulnerability was published Sep 12, 2026; the highest published CVSS base score is 7.2.
Plugin slug:
temporary-login-without-passwordLatest vulnerability
CVE-2026-77753: Temporary Login Without Password: A security weakness
Temporary Login Without Password is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is < 1.9.9.
| Safe version |
|
||
|---|---|---|---|
| Sep 12, 2026 |
CVE-2026-77753
Temporary Login Without Password: A security weakness
Temporary Login Without Password is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is < 1.9.9.
|
1.9.9 |
CVE5.5
NVDPending
|
| Sep 12, 2026 |
CVE-2026-77752
Temporary Login Without Password lets site admins take over multisite
Temporary Login Without Password from 1.5 through versions before 1.9.9 fails to require network-super-admin authority before granting those rights to a temporary or existing account. A single-site administrator on WordPress multisite can promote their own account or another account and take over the network. The authoritative export does not name the handler or privilege field.
|
1.9.9 |
CVE7.2
NVDPending
|
| Dec 13, 2021 |
CVE-2021-24836
Temporary Login Without Password: Cross-site request forgery
Temporary Login Without Password is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
|
See mitigation notes |
CVEPending
NVD4.3
|