WordPress security changelog
HIGH CVE-2025-1717 Modified

Login Me Now: Privilege escalation or authentication bypass

Login Me Now is affected by privilege escalation or authentication bypass. The vulnerable path is reachable without authentication. A successful request can grant permissions or access that the caller should not possess.

CVE / CNA score 8.1 CVSS 3.1 · security@wordfence.com
NVD score 8.1 CVSS 3.1 · nvd@nist.gov
Component
Login Me Now
Plugin slug
login-me-now
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Feb 27, 2025
Weakness
CWE-288 — Authentication Bypass Using an Alternate Path or Channel
CWE-306 — Missing Authentication for Critical Function

This CVE was published Feb 27, 2025 and is one of 1 known issue for this plugin.

Update, patch or deactivate.

Update Login Me Now to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Technical description

The Login Me Now plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 1.7.2. This is due to insecure authentication based on an arbitrary transient name in the 'AutoLogin::listen()' function. This makes it possible for unauthenticated attackers to log in an existing user on the site, even an administrator. Note: this vulnerability requires using a transient name and value from another software, so the plugin is not inherently vulnerable on it's own.

CVE / CNA vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

NVD vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Primary and upstream sources