dbcve.org
Customize My AccountWordPress extension · Sysbasics

CVE-2023-51369

HIGH · 8.8 CVSS v3.1 Published 2024-03-15
Fix available
A fix is available. Upgrade to 1.8.4 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 SysBasics Customize My Account for WooCommerce.This issue affects Customize My Account for WooCommerce: from n/a through 1.8.3.

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 SysBasics Customize My Account for WooCommerce plugin versions up to 1.8.3 allows attackers to trick authenticated users into performing unintended account modifications by forging requests, as the plugin lacks proper anti-CSRF token validation on state-changing actions.

MitigationImplement WordPress nonces (anti-CSRF tokens) on all forms and AJAX actions within the plugin, and verify the nonce validation on server-side processing before executing any state-changing operations.

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
Customize My AccountWordPress extension
Affected:< 1.8.4

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
    Log into WordPress admin, go to Plugins > Installed Plugins, and look for 'Sysbasins Customize My Account for WooCommerce' or search for 'Customize My Account'
    Affected if The plugin does not appear in the installed plugins list, then the site is not affected by this specific vulnerability
  2. Check if the plugin is active
    In the Plugins list, verify whether 'Sysbasins Customize My Account for WooCommerce' shows as 'Active'
    Affected if The plugin is installed but not active, then it cannot be exploited
  3. Determine the installed version
    In the Plugins list, click on the plugin name or view the plugin details to see the version number displayed. Alternatively, open the main plugin file (customize-my-account-for-woocommerce.php) in wp-content/plugins/customize-my-account-for-woocommerce/ and look for the 'Version:' header in the plugin comment block
    Affected if The version is 1.8.3 or lower (anything below 1.8.4), the site is within the affected version range
  4. Inspect plugin files for nonce validation on state-changing actions
    Review the main plugin PHP files, particularly any that handle form submissions or AJAX actions. Look for calls to wp_verify_nonce(), check_admin_referer(), or wp_nonce_field() before any insert, update, or delete operations. Check files that handle account modifications like profile updates, order changes, or settings changes
    Affected if State-changing functions (such as saving user settings, updating account data, or modifying WooCommerce endpoints) lack nonce verification code, the CSRF protection is missing and the site is vulnerable

A site is affected if the Sysbasins Customize My Account for WooCommerce plugin is active with version 1.8.3 or lower AND the plugin's state-changing actions do not validate anti-CSRF tokens.

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.8.4 or later
Fixed in 1.8.4
Interim mitigation

Implement WordPress nonces (anti-CSRF tokens) on all forms and AJAX actions within the plugin, and verify the nonce validation on server-side processing before executing any state-changing operations.

Recommended fix High confidence

1.8.4 or later

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Customize My Account for WooCommerce' in the plugin list
  4. Check if the current version is below 1.8.4
  5. If vulnerable, click 'Update Now' to update to the latest version (1.8.4 or later)
  6. After update, verify the plugin version shows 1.8.4 or higher
  7. Test critical user account functionality to ensure the update did not break existing functionality
Caveat Review plugin changelog for any breaking changes before updating, and test in staging if possible

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

Fix this in Customize My Account 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-51369 — 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-51369 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