dbcve.org
Store Exporter For WoocommerceWordPress extension · Visser

CVE-2023-46822

MEDIUM · 6.1 CVSS v3.1 Published 2023-11-06
Fix available
A fix is available. Upgrade to after 2.7.2 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
Unauth. Reflected Cross-Site Scripting') vulnerability in Visser Labs Store Exporter for WooCommerce – Export Products, Export Orders, Export Subscriptions, and More plugin <= 2.7.2 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

An unauthenticated reflected cross-site scripting (XSS) vulnerability exists in the Visser Labs Store Exporter for WooCommerce plugin. The vulnerability allows attackers to inject malicious JavaScript through unsanitized user input that gets reflected in the page without proper output encoding.

MitigationUpdate the plugin to a version higher than 2.7.2 which contains the security patch; alternatively, disable the plugin until an update is available.

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
Store Exporter For WoocommerceWordPress extension
Affected:<= 2.7.2

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 the plugin is installed
    Check your WordPress site's plugins directory for the 'Visser Store Exporter For WooCommerce' or 'visser-store-exporter-woocommerce' plugin folder
    Affected if The plugin folder exists in your WordPress plugins directory
  2. Identify the installed version
    Open the main plugin file (typically named plugin-name.php) and locate the version header in the plugin comment block, or check the readme.txt file for the 'Stable tag' version entry
    Affected if The version displayed is 2.7.2 or any version lower than 2.7.2
  3. Confirm the plugin is active
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins, or query the WordPress database plugins table to verify the plugin status is 'active'
    Affected if The plugin is enabled and active on the site
  4. Verify the vulnerability is exploitable
    This is a reflected XSS requiring no authentication - if the plugin is active and the version is <= 2.7.2, the unsanitized user input reflection point exists in the plugin's frontend or admin ajax handlers
    Affected if The plugin version is <= 2.7.2 and the plugin is actively processing requests

Your environment is affected if the Visser Store Exporter For WooCommerce plugin is installed with version 2.7.2 or lower and is currently active on your WordPress site.

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

Update the plugin to a version higher than 2.7.2 which contains the security patch; alternatively, disable the plugin until an update is available.

Recommended fix Moderate confidence

2.7.3 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Store Exporter for WooCommerce' by Visser Labs
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from the WordPress Plugin Repository or from Visser Labs
  6. 6. Deactivate and re-activate the plugin if needed after update
  7. 7. Verify the update was successful by checking the plugin version

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

Fix this in Store Exporter For Woocommerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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