dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-12137

MEDIUM · 6.1 CVSS v3.1 Published 2026-06-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The SysBasics Customize My Account for WooCommerce – Dashboard, Endpoints, Avatar & Menu Manager plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'tab' parameter in all versions up to, and including, 4.3.6 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. Because the vulnerable plugin_options_page() function is only rendered within the WordPress admin dashboard, successful exploitation requires the targeted victim to be logged in with Shop Manager-level access or higher.

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

This is a reflected XSS vulnerability in the SysBasics Customize My Account for WooCommerce plugin where the 'tab' parameter in the admin settings page is not sanitized before output, allowing injection of arbitrary JavaScript. The attack requires the victim to be logged in with Shop Manager-level access or higher and tricking them into clicking a malicious link.

MitigationUpdate the plugin to version 4.3.7 or later which includes proper sanitization of the 'tab' parameter using WordPress sanitization functions and output escaping.

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
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 for the existence of the SysBasics Customize My Account for WooCommerce plugin in wp-content/plugins/ directory or via WordPress admin plugins list
    Affected if Plugin is present in the installation
  2. Identify installed version
    Check the plugin header in main PHP file or view version in WordPress admin plugins list
    Affected if Version is lower than 4.3.7 or version cannot be determined
  3. Confirm admin access exists
    Verify there are users with Shop Manager-level (or higher) privileges in WordPress users panel
    Affected if Users with Shop Manager or Administrator roles exist
  4. Inspect tab parameter handling
    Examine the plugin PHP code that handles the 'tab' parameter in admin settings - look for unsanitized $_GET['tab'] output before fixed version 4.3.7
    Affected if Code shows 'tab' parameter is output without sanitization functions like esc_html() or esc_attr()
  5. Check for malicious link exposure
    Review server access logs or browser history for any suspicious URLs containing 'tab=' parameter with script tags pointing to wp-admin/admin.php?page=wc-settings&tab=
    Affected if Suspicious XSS payloads found in logs or URL parameters

User is affected if the plugin is installed with version lower than 4.3.7 AND users with Shop Manager-level access exist in the WordPress installation.

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

Update the plugin to version 4.3.7 or later which includes proper sanitization of the 'tab' parameter using WordPress sanitization functions and output escaping.

Recommended fix Moderate confidence

Version 4.3.7 or latest available version (check WordPress Plugin Repository for current release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'SysBasics Customize My Account for WooCommerce'
  4. Check the current version is at least 4.3.7 or later (the first version containing the security fix)
  5. If the plugin shows a version lower than 4.3.7, click 'Update Now' to install the latest version
  6. After updating, verify the 'tab' parameter is properly sanitized by testing the plugin's settings pages

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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