dbcve.org
Store Exporter For WoocommerceWordPress extension · Visser

CVE-2024-8793

MEDIUM · 6.1 CVSS v3.1 Published 2024-10-01
Fix available
A fix is available. Upgrade to after 2.7.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
The Store Exporter for WooCommerce – Export Products, Export Orders, Export Subscriptions, and More plugin for WordPress is vulnerable to Reflected Cross-Site Scripting due to the use of add_query_arg without appropriate escaping on the URL in all versions up to, and including, 2.7.2.1. 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.

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 Cross-Site Scripting (XSS) vulnerability in the Store Exporter for WooCommerce WordPress plugin. The vulnerability exists because the plugin uses WordPress's add_query_arg() function to build URLs without properly escaping the output. Unauthenticated attackers can craft malicious URLs containing JavaScript payloads that execute in a victim's browser when they click on a specially crafted link.

MitigationUpdate the plugin to version 2.7.2.2 or later, which contains the patched code. Until then, users should avoid clicking untrusted links and site administrators can implement Content Security Policy (CSP) headers as a defense-in-depth measure.

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.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. Confirm the plugin is installed and active
    Navigate to WordPress Admin > Plugins and verify 'Store Exporter for WooCommerce' or 'Visser Store Exporter for WooCommerce' is installed and activated
    Affected if The plugin is installed and active on the WordPress site
  2. Check the installed plugin version
    In WordPress Admin > Plugins, find the plugin and view the version number displayed beneath the plugin name. Compare against the affected range: versions 2.7.2.1 and below are vulnerable
    Affected if The installed version is 2.7.2.1 or lower
  3. Inspect plugin source code for unsafe add_query_arg usage
    Locate the plugin files in wp-content/plugins/ and search for add_query_arg() function calls that output URLs without applying esc_url(), esc_attr(), or similar escaping functions
    Affected if The plugin code contains add_query_arg() calls that directly output URLs to the browser without proper escaping
  4. Verify lack of output escaping in URL generation
    Examine PHP files in the plugin that handle URL construction, specifically looking for instances where add_query_arg() results are echoed or returned without sanitization
    Affected if URLs generated by the plugin are not escaped before being output to HTML
  5. Check for Content Security Policy header as defense-in-depth
    Inspect HTTP response headers for a Content-Security-Policy header that would help mitigate XSS execution
    Affected if No CSP header is present and the plugin is vulnerable, increasing exposure to reflected XSS attacks

A user is affected if the plugin is installed at version 2.7.2.1 or below and uses the vulnerable URL generation code without compensating controls like CSP headers.

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.

From vendor data
Upgrade available Upgrade to a release after 2.7.2.1
Interim mitigation

Update the plugin to version 2.7.2.2 or later, which contains the patched code. Until then, users should avoid clicking untrusted links and site administrators can implement Content Security Policy (CSP) headers as a defense-in-depth measure.

Fix this in Store Exporter For Woocommerce 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 the upgrade done

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-2024-8793 — 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-2024-8793 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