Temporary Login Without Password < 1.9.9 - Authenticated (Custom Role+) Persistent Access After Login Revocation
Strategic Overview
- Status
- Patched in 1.9.9
- Affected Plugin
- Temporary Login Without Password
- Affected Version
< 1.9.9- CVSS
- 4.3Medium
- Weakness type
- CWE-287 · Improper Authentication
- CVE
CVE-2026-77753
At a glance
CVE-2026-77753 is a medium-severity Improper Authentication vulnerability in the Temporary Login Without Password WordPress plugin, affecting versions < 1.9.9. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Custom Role level or above. The issue is fixed in version 1.9.9; sites on affected versions should update now. Disclosed September 2026, reported by BaptouTatis.
Vulnerability Overview
The Temporary Login Without Password plugin for WordPress is vulnerable to broken authentication in all versions up to 1.9.9 (exclusive). This is due to the plugin not revoking authorization after login revocation. This makes it possible for authenticated attackers, with Custom-level access and above, to utilize application passwords even after their account has been revoked.
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 interaction from a victim user.
CWE-287: Improper Authentication
Reaching this weakness in Temporary Login Without Password < 1.9.9 takes an account at Custom Role level or above. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.
An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. For Temporary Login Without Password the fix is 1.9.9: builds < 1.9.9 are affected, anything from 1.9.9 onward is not.
Remediation
Update to version 1.9.9, 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 Without Password 1.9.9 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Temporary Login Without Password
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C