dbcve.org
Smart Online Order For CloverWordPress extension · Zaytech

CVE-2024-7032

MEDIUM · 6.5 CVSS v3.1 Published 2024-08-21
Fix available
A fix is available. Upgrade to 1.5.7 or later.
See remediation →
74/100
Remediation priority · Elevated
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 Smart Online Order for Clover plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the 'moo_deactivateAndClean' function in all versions up to, and including, 1.5.6. This makes it possible for unauthenticated attackers to deactivate the plugin and drop all plugin tables from the database.

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 Smart Online Order for Clover WordPress plugin is vulnerable to broken access control. The 'moo_deactivateAndClean' function lacks a capability check, allowing any unauthenticated user to trigger it. This function both deactivates the plugin and drops all plugin database tables, resulting in complete data loss.

MitigationAdd a WordPress capability check (e.g., current_user_can('manage_options')) at the beginning of the moo_deactivateAndClean function to ensure only authenticated administrators can execute this destructive operation. Also consider adding nonce verification for additional security.

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
Smart Online Order For CloverWordPress extension
Affected:< 1.5.7

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

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

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 plugin installation
    Navigate to WordPress admin > Plugins and verify 'Smart Online Order for Clover' by Zaytech is installed, or check filesystem for /wp-content/plugins/smart-online-order-for-clover/ directory
    Affected if Plugin is installed and active
  2. Identify installed version
    Check the plugin version in the plugin header (wp-admin > Plugins > Smart Online Order for Clover) or in the main plugin PHP file header comment
    Affected if Version is less than 1.5.7 (e.g., 1.5.6, 1.5.5, etc.)
  3. Locate vulnerable function
    Open the main plugin file (usually moo-OnlineOrders.php or similar) and search for the function 'moo_deactivateAndClean'
    Affected if Function exists in the plugin code
  4. Verify missing capability check
    Within the moo_deactivateAndClean function, search for 'current_user_can' or any capability check at the function's beginning. If no such check exists, the vulnerability is present
    Affected if No capability check (e.g., current_user_can('manage_options')) is found at the start of moo_deactivateAndClean function

You are affected if the plugin is installed with a version below 1.5.7 AND the moo_deactivateAndClean function lacks a capability check, allowing unauthenticated users to trigger complete data loss.

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 1.5.7 or later
Fixed in 1.5.7
Interim mitigation

Add a WordPress capability check (e.g., current_user_can('manage_options')) at the beginning of the moo_deactivateAndClean function to ensure only authenticated administrators can execute this destructive operation. Also consider adding nonce verification for additional security.

Recommended fix High confidence

1.5.7

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Smart Online Order For Clover' in the plugin list
  4. Check if current version is below 1.5.7
  5. If vulnerable, click 'Update Now' to upgrade to version 1.5.7
  6. Alternatively, navigate to Dashboard > Updates and update all plugins
  7. Verify the plugin has been updated to version 1.5.7 or higher after completion

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

Fix this in Smart Online Order For Clover Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
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,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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