dbcve.org
NextmoveWordPress extension · Xlplugins

CVE-2024-25092

HIGH · 8.8 CVSS v3.1 Published 2024-06-09
Fix available
A fix is available. Upgrade to 2.18.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Missing Authorization vulnerability in XLPlugins NextMove Lite.This issue affects NextMove Lite: from n/a through 2.17.0.

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 · moderate confidence

This is a Missing Authorization (Broken Access Control) vulnerability in the XLPlugins NextMove Lite WordPress plugin. The flaw allows unauthenticated or unauthorized users to access functionality that should require proper capability checks, potentially leading to unauthorized configuration changes or data access.

MitigationApply the latest security patch from XLPlugins (version 2.17.1 or higher). If no patch is available, manually add proper capability checks and nonce verification to all AJAX handlers and admin functions in the plugin.

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
NextmoveWordPress extension
Affected:< 2.18.0

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify NextMove Lite plugin is installed
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'NextMove Lite' or 'NextMove' by XLPlugins in the list of active plugins.
    Affected if The plugin is present and active in the WordPress installation.
  2. Check the installed plugin version
    In the Plugins list, click on 'View Details' next to the NextMove Lite plugin, or check the main plugin file (usually wp-content/plugins/nextmove-lite/nextmove-lite.php) for the 'Version' header in the plugin comments.
    Affected if The displayed version number is lower than 2.18.0 (for example, 2.17.0, 2.16.0, or earlier).
  3. Identify exposed AJAX handlers
    Search the plugin directory for PHP files containing 'add_action( 'wp_ajax_' )' or 'add_action( 'wp_ajax_nopriv_' )' calls. These are AJAX endpoints that may be accessible. Review whether these handlers include capability checks using 'current_user_can()' or 'check_ajax_referer()'.
    Affected if AJAX handlers are found that lack proper capability checks or nonce verification, or if 'wp_ajax_nopriv_' actions exist for sensitive operations.
  4. Test admin function accessibility
    Attempt to access plugin admin pages or functions directly via URL without logging in or without administrator privileges. Observe whether access is granted to configuration pages, thank you page settings, or order data that should require admin authentication.
    Affected if Unauthenticated or lower-privilege users can access admin-only plugin functionality or view/edit plugin settings without proper authorization.

A user is affected if the NextMove Lite plugin version is below 2.18.0 and AJAX handlers or admin functions lack proper capability checks, allowing unauthorized access to sensitive plugin features.

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.

dbcve · scoped
Upgrade available Upgrade to 2.18.0 or later
Fixed in 2.18.0
Interim mitigation

Apply the latest security patch from XLPlugins (version 2.17.1 or higher). If no patch is available, manually add proper capability checks and nonce verification to all AJAX handlers and admin functions in the plugin.

Recommended fix High confidence

NextMove Lite version 2.18.0 or later

  1. 1. Backup your WordPress site and database before performing any updates
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Find NextMove Lite (XLPlugins NextMove Lite) in the plugins list
  4. 4. If an update is available, click 'Update Now' to update to version 2.18.0 or later
  5. 5. Alternatively, download version 2.18.0 or latest from the WordPress plugin repository and upload manually
  6. 6. After updating, verify the plugin version shows 2.18.0 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nextmove Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-25092 — 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-2024-25092 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