dbcve.org
Custom My Account For WoocommerceWordPress extension · Phoeniixx

CVE-2023-46634

MEDIUM · 6.1 CVSS v3.1 Published 2023-11-13
Fix available
A fix is available. Upgrade to after 2.1 or later.
See remediation →
68/100
Remediation priority · Elevated
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 phoeniixx Custom My Account for Woocommerce allows Cross-Site Scripting (XSS).This issue affects Custom My Account for Woocommerce: from n/a through 2.1.

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

A CSRF vulnerability in the phoeniixx Custom My Account for WooCommerce plugin (versions up to 2.1) allows attackers to trick authenticated administrators or users into performing actions that inject malicious JavaScript (XSS) into the My Account pages. This is a chained vulnerability where CSRF bypasses the Same-Origin Policy check to deliver stored XSS payloads.

MitigationUpdate the plugin to the latest patched version released by phoeniixx. If no patch is available, disable the plugin until a fix is published, and review admin/user sessions for compromise.

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 My Account For WoocommerceWordPress extension
Affected:<= 2.1

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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 plugin is installed
    Check if the phoeniixx Custom My Account for WooCommerce plugin is present in the WordPress plugins directory (wp-content/plugins/) or via the WordPress admin plugins list
    Affected if The plugin is installed and active on the WordPress site
  2. Identify installed plugin version
    Locate the plugin main PHP file (typically named index.php, main.php, or phoeniixx-custom-my-account.php within the plugin folder) and look for a version comment/constant, or check the WordPress plugin admin panel version column
    Affected if The installed version is 2.1 or lower
  3. Confirm My Account feature is enabled
    Access the WooCommerce My Account pages in the frontend while logged in as a user or administrator to verify the custom My Account functionality is rendering
    Affected if Custom My Account pages are being displayed to users
  4. Inspect My Account page source for injected scripts
    View the HTML source of the My Account page (right-click > View Page Source) and search for any script tags, inline JavaScript, or suspicious external resource references that were not intentionally added by the site administrator
    Affected if Unexpected script tags or malicious JavaScript are present in the My Account page HTML

The site is affected if the phoeniixx Custom My Account for WooCommerce plugin version 2.1 or lower is installed and active with the My Account feature enabled, allowing CSRF-triggered XSS payloads to execute.

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

Update the plugin to the latest patched version released by phoeniixx. If no patch is available, disable the plugin until a fix is published, and review admin/user sessions for compromise.

Recommended fix Moderate confidence

Version 2.2 or latest available release

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Custom My Account for Woocommerce' by phoeniixx
  4. Check if update to version 2.2 or later is available
  5. If update available, click 'Update Now' to install the patched version
  6. If no update visible, check the WordPress plugin repository or contact phoeniixx directly for the patched release
  7. Verify the plugin was updated successfully after completion

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

Fix this in Custom My Account For Woocommerce Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
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,840.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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