dbcve.org
Woo Custom And Sequential Order NumberWordPress extension · Vjinfotech

CVE-2023-47687

HIGH · 8.8 CVSS v3.1 Published 2023-11-16
Fix available
A fix is available. Upgrade to after 2.6.0 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 VJInfotech Woo Custom and Sequential Order Number plugin <= 2.6.0 versions.

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 VJInfotech Woo Custom and Sequential Order Number plugin versions 2.6.0 and below allows attackers to trick authenticated administrators into performing unintended actions such as modifying order number settings or configuration changes via maliciously crafted requests.

MitigationImplement anti-CSRF tokens (nonces) on all plugin forms and AJAX endpoints, and verify these nonces on the server side before processing any state-changing requests.

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
Woo Custom And Sequential Order NumberWordPress extension
Affected:<= 2.6.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
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. Identify plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Woo Custom and Sequential Order Number' by VJInfotech. Note the version number displayed. Alternatively, check the plugin's main PHP file header or the readme.txt file in the plugin directory.
    Affected if The installed version is 2.6.0 or lower.
  2. Locate plugin admin pages and forms
    Navigate to WooCommerce > Order Number (or similar menu item added by the plugin). Identify all forms that allow settings changes, such as order number prefix/suffix configuration, starting numbers, or sequence settings.
    Affected if Forms exist that modify plugin configuration without visible nonce token fields.
  3. Inspect form HTML for nonce fields
    View the page source (right-click > View Page Source) of the plugin's settings pages. Search for 'wp_nonce' or '_wpnonce' fields within the form tags. Look for input fields with names containing 'nonce' or '_token'.
    Affected if No nonce or token input fields are present in the configuration forms.
  4. Check AJAX endpoints for nonce verification
    Examine the plugin's JavaScript files (usually in /js/ folder) and look for AJAX calls (jQuery.ajax, wp.ajax). Identify the action names being used. Then review the plugin PHP code for those AJAX handlers and check if they call 'check_ajax_referer' or 'wp_verify_nonce'.
    Affected if AJAX endpoints that modify settings do not verify nonces before processing requests.
  5. Verify nonce validation in form processing
    Review the plugin's PHP handler that processes form submissions (usually in the main plugin file or a separate admin class). Look for the presence of 'check_admin_referer', 'wp_verify_nonce', or 'wp_create_nonce' calls before any database updates or configuration changes.
    Affected if Form submission handlers lack nonce verification and proceed directly to update functions.

You are affected if the plugin version is 2.6.0 or lower and the admin forms/AJAX endpoints lack nonce token validation before processing configuration changes.

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 a release after 2.6.0
Interim mitigation

Implement anti-CSRF tokens (nonces) on all plugin forms and AJAX endpoints, and verify these nonces on the server side before processing any state-changing requests.

Recommended fix Moderate confidence

2.6.1 or latest stable release

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Woo Custom and Sequential Order Number plugin
  4. 4. If an update is available, click 'Update Now' to update to the latest version
  5. 5. After updating, verify the plugin is running version 2.6.1 or higher
  6. 6. Test order number generation functionality to confirm the update did not break existing functionality

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

Fix this in Woo Custom And Sequential Order Number Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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