CVE-2025-1717: The Login Me Now plugin for WordPress is vulnerable to authentication bypass in versions up to, and including,

Q: How do I fix CVE-2025-1717?

login me now: upgrade to newer than 1.7.2. Exact commands for each OS are on this page.

Q: Is CVE-2025-1717 being exploited?

CVE-2025-1717 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-1717 affect?

CVE-2025-1717 affects login me now. Severity is high (CVSS 8.1). 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 ma

Q: How urgent is CVE-2025-1717?

Priority 45/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 8.1REMOTEUPGRADE

CVE-2025-1717 is a high-severity flaw (CVSS 8.1) affecting login me now. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 plug

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.6% (top 52%)
CISA exploited list	No
Weakness	CWE-288, CWE-306
Published	2025-02-27
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: pluginly

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-02-27 08:15 UTCPublished CVE record published
2026-06-17 08:39 UTCUpdated Record last modified

pluginly login me now UPGRADE

Affected: <= 1.7.2

Fixed in: newer than 1.7.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy login-me-now || rpm -q login-me-now || login-me-now --version

2. UPGRADE to newer than 1.7.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade login-me-now

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade login-me-now

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-1717?

Is CVE-2025-1717 being exploited?

CVE-2025-1717 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-1717 affect?

CVE-2025-1717 affects login me now. Severity is high (CVSS 8.1). 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 ma

How urgent is CVE-2025-1717?

Priority 45/100. High severity; Remotely exploitable, no login, no user action

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs