CVE-2024-10860

NextMove Lite – Thank You Page for WooCommerce <= 2.19.0 - Missing Authorization to Authenticated (Subscriber+) Deactivation Reason Submission

2025-02-27 00:00
incognito

Strategic Overview

Status
Patched in 2.20.0
Affected Plugin
NextMove Lite – Thank You Page for WooCommerce
Affected Version
<= 2.19.0
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-10860
View all NextMove Lite – Thank You Page for WooCommerce vulnerabilities

At a glance

CVE-2024-10860 is a medium-severity Missing Authorization vulnerability in the NextMove Lite WordPress plugin, affecting versions <= 2.19.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.20.0; sites on affected versions should update now. Disclosed February 2025, reported by incognito.

Vulnerability Overview

The NextMove Lite – Thank You Page for WooCommerce plugin for WordPress is vulnerable to unauthorized submission of data due to a missing capability check on the _submit_uninstall_reason_action() function in all versions up to, and including, 2.19.0. This makes it possible for authenticated attackers, with Subscriber-level access and above, to submit a deactivation reason on behalf of a site.

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-862: Missing Authorization

NextMove Lite <= 2.19.0 carries this weakness at _submit_uninstall_reason_action(), and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For NextMove Lite the fix is 2.20.0: builds <= 2.19.0 are affected, anything from 2.20.0 onward is not.

Remediation

Update to version 2.20.0, 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: NextMove Lite 2.20.0 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-10860https://www.wordfence.com/threat-intel/vulnerabilities/id/5cefecf8-46dc-4ae1-9e94-b724beb7136fhttps://nvd.nist.gov/vuln/detail/CVE-2024-10860

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C