dbcve.org
Custom Order Status Manager For WoocommerceWordPress extension · Nuggethon

CVE-2024-25930

HIGH · 8.8 CVSS v3.1 Published 2024-02-29
Fix available
A fix is available. Upgrade to after 1.5.2 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Nuggethon Custom Order Statuses for WooCommerce.This issue affects Custom Order Statuses for WooCommerce: from n/a through 1.5.2.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Nuggethon Custom Order Statuses for WooCommerce plugin. The plugin fails to properly validate the origin of requests, allowing attackers to trick authenticated administrators into performing unintended actions such as creating, modifying, or deleting custom order statuses via malicious links or embedded forms.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) on all state-changing operations and validate Origin/Referer headers. Update to the latest patched version if available.

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
Custom Order Status Manager For WoocommerceWordPress extension
Affected:<= 1.5.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
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and search for 'Nuggethon Custom Order Status Manager For Woocommerce' or 'Custom Order Status', or inspect the /wp-content/plugins/ directory for a folder matching the plugin name
    Affected if The plugin is present in the WordPress installation
  2. Confirm the installed version
    In the WordPress Plugins list, locate the plugin and note the version number displayed under the plugin name, or open the main plugin PHP file and look for the 'Version' header in the plugin comment block
    Affected if The installed version is 1.5.2 or lower (any version up to and including 1.5.2)
  3. Inspect state-changing functions for anti-CSRF tokens
    Examine the plugin PHP files (particularly those handling order status create/modify/delete actions) and search for 'wp_nonce_field', 'wp_nonce_url', 'check_admin_referer', or 'check_ajax_referer' function calls within the forms or AJAX handlers that modify order statuses
    Affected if No anti-CSRF tokens (nonces) are found in the code handling custom order status changes, or the nonces are missing from the forms/requests that create, modify, or delete order statuses
  4. Check for Origin/Referer header validation
    Review the plugin's PHP files for code that validates the 'Origin' or 'HTTP_REFERER' server variables before processing state-changing requests
    Affected if No validation of Origin or Referer headers is performed on requests that modify order statuses

You are affected if the Nuggethon Custom Order Status Manager For Woocommerce plugin is installed at version 1.5.2 or lower AND the plugin code lacks anti-CSRF token validation on its order status modification functions.

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.5.2
Interim mitigation

Implement anti-CSRF tokens (synchronizer token pattern) on all state-changing operations and validate Origin/Referer headers. Update to the latest patched version if available.

Fix this in Custom Order Status Manager For Woocommerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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