dbcve.org
Login Me NowWordPress extension · Pluginly

CVE-2025-1717

HIGH · 8.1 CVSS v3.1 Published 2025-02-27
Fix available
A fix is available. Upgrade to after 1.7.2 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Login Me Now WordPress plugin versions up to 1.7.2 contain an authentication bypass vulnerability in the AutoLogin::listen() function. The function uses an arbitrary transient name for authentication, allowing unauthenticated attackers to log in as any existing user on the site, including administrators. The attack requires knowledge of a transient name and value from another software component, making the plugin dependent on external software state.

MitigationUpdate the Login Me Now plugin to the latest version once available. Audit user accounts for unauthorized access and rotate credentials. Investigate what other software on the site uses transients that could be leveraged for this attack.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Login Me NowWordPress extension
Affected:<= 1.7.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Login Me Now plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Login Me Now' or 'Pluginly Login Me Now'. Note the version number displayed below the plugin name.
    Affected if Plugin is installed with version 1.7.2 or lower.
  2. Identify the installed version number
    Check the plugin header file (login-me-now.php) or the WordPress plugin page for the exact version. Compare against the affected range: <= 1.7.2.
    Affected if Installed version is 1.7.2 or any version up to and including 1.7.2.
  3. Determine if AutoLogin feature is enabled
    Navigate to the plugin settings in WordPress admin (usually under Settings > Login Me Now or similar). Look for an AutoLogin, Auto Sign-In, or automatic login feature toggle. Check the database options table (wp_options) for option names containing 'login_me_now_autologin' or similar AutoLogin settings set to enabled/true.
    Affected if AutoLogin feature is enabled and the plugin version is <= 1.7.2.
  4. Review user accounts for unauthorized access
    In WordPress admin, go to Users > All Users. Look for: (1) newly created administrator accounts you did not create, (2) unexpected users added recently, (3) users with roles changed to administrator. Check user metadata for recent login timestamps that do not match your records.
    Affected if Any unexpected administrator accounts exist or there are login records for users at times you did not authorize.

A user is affected if the Login Me Now plugin version is 1.7.2 or lower AND the AutoLogin feature is enabled, especially if unauthorized admin accounts or anomalous login activity are present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 1.7.2
Interim mitigation

Update the Login Me Now plugin to the latest version once available. Audit user accounts for unauthorized access and rotate credentials. Investigate what other software on the site uses transients that could be leveraged for this attack.

Fix this in Login Me Now Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1717 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-1717 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data