dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-31921

HIGH · 8.2 CVSS v3.1 Published 2026-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/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
Missing Authorization vulnerability in Devteam HaywoodTech Product Rearrange for WooCommerce products-rearrange-woocommerce allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Product Rearrange for WooCommerce: from n/a through <= 1.2.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

The Product Rearrange for WooCommerce plugin (versions up to 1.2.2) contains a Missing Authorization vulnerability where access control checks are not properly enforced on certain functionality. This allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized users to manipulate product ordering and other administrative functions without proper authentication or authorization.

MitigationUpdate to the latest version of Product Rearrange for WooCommerce when available, or implement proper capability checks and nonce validation on all sensitive endpoints until a patched version is released.

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

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
High
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Verify Product Rearrange for WooCommerce is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'product-rearrange-for-woocommerce' or similar, or query the wp_options table for the active_plugins list
    Affected if The plugin folder exists in the WordPress installation and is activated in the Plugins admin page
  2. Determine the installed plugin version
    Read the main plugin file header (usually product-rearrange-for-woocommerce.php) and locate the 'Version' comment, or check the WordPress plugins admin page for the installed version
    Affected if The version is 1.2.2 or any version lower than 1.2.2 (the vulnerability affects versions up to and including 1.2.2)
  3. Confirm WooCommerce is active
    Check that WooCommerce is installed and activated, since this is a WooCommerce-dependent plugin; verify in Plugins admin or query wp_options for active_plugins containing 'woocommerce'
    Affected if WooCommerce is active and the Product Rearrange plugin is also active - the vulnerability only applies in this combined state
  4. Inspect main plugin file for capability checks
    Open the primary plugin PHP file and search for function calls like 'current_user_can', 'check_admin_referer', 'wp_verify_nonce', or 'capability' near sensitive functions that handle product reordering
    Affected if No capability checks (like current_user_can('manage_woocommerce')) are found before sensitive operations, indicating missing authorization
  5. Check AJAX handlers for authorization
    Locate AJAX action hooks (add_action('wp_ajax_...')) in the plugin files and verify whether they include nonce validation or capability checks before processing requests
    Affected if AJAX endpoints that modify product ordering lack nonce verification or current_user_can() checks, allowing unauthorized access

If Product Rearrange for WooCommerce is installed at version 1.2.2 or below and WooCommerce is active, the environment is likely affected by this missing authorization vulnerability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of Product Rearrange for WooCommerce when available, or implement proper capability checks and nonce validation on all sensitive endpoints until a patched version is released.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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