dbcve.org
Custom Order Numbers For WoocommerceWordPress extension · Tychesoftwares

CVE-2022-45367

HIGH · 8.8 CVSS v3.1 Published 2023-05-25
Fix available
A fix is available. Upgrade to after 1.4.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 Tyche Softwares Custom Order Numbers for WooCommerce plugin <= 1.4.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 · high confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Custom Order Numbers for WooCommerce plugin allows attackers to trick authenticated administrators into performing unintended actions (such as modifying order number settings) by crafting malicious requests that the server accepts without proper token validation.

MitigationUpdate the plugin to version 1.4.1 or later which includes anti-CSRF token validation; alternatively, implement nonce verification on all state-changing admin actions and validate Origin/Referer headers.

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 Numbers For WoocommerceWordPress extension
Affected:<= 1.4.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. Check plugin version in WordPress admin
    Go to WordPress Admin > Plugins > Installed Plugins. Locate 'Custom Order Numbers for WooCommerce' by Tychesoftwares and note the version number displayed in the plugin description column.
    Affected if The version shown is 1.4.0 or any version number lower than 1.4.0 (for example, 1.3.9, 1.3.0, 1.2.5, etc.)
  2. Verify plugin version via file inspection
    Access the plugin directory via FTP or file manager. Navigate to wp-content/plugins/custom-order-numbers-for-woocommerce/ and open the main plugin file (usually custom-order-numbers-for-woocommerce.php or similar). Look for the 'Version:' header in the plugin file comments.
    Affected if The Version header in the plugin file reads 1.4.0 or lower
  3. Check plugin file for nonce implementation
    In the plugin directory, search the PHP files that handle admin settings or state-changing actions (typically files with 'admin', 'settings', or 'order' in the name). Look for the presence of wp_verify_nonce or check_admin_referer function calls on form submissions or action handlers.
    Affected if The plugin files handling admin actions lack nonce verification functions, or the vulnerability remains unpatched (version <= 1.4.0 indicates this automatically)

The environment is affected if the installed Custom Order Numbers for WooCommerce plugin version is 1.4.0 or lower, as this version lacks CSRF token validation on admin actions.

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 1.4.0
Interim mitigation

Update the plugin to version 1.4.1 or later which includes anti-CSRF token validation; alternatively, implement nonce verification on all state-changing admin actions and validate Origin/Referer headers.

Recommended fix High confidence

1.4.1

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Custom Order Numbers for WooCommerce' by Tyche Softwares
  4. Check the current version installed (should be 1.4.0 or below)
  5. Click 'Update now' if an update is available, or manually download version 1.4.1 from the WordPress plugin repository
  6. After updating, verify the new version number reflects 1.4.1
  7. Test that the WooCommerce order number functionality still works correctly

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

Fix this in Custom Order Numbers For Woocommerce 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-2022-45367 — 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-2022-45367 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