dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-13623

MEDIUM · 5.9 CVSS v3.1 Published 2025-01-31
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 Zero-click

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 Order Export for WooCommerce plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.24 via the 'uploads' directory. This makes it possible for unauthenticated attackers to extract sensitive data stored insecurely in the /wp-content/uploads directory which can contain exported order information. The plugin is only vulnerable when 'Order data storage' is set to 'WordPress posts storage (legacy)', and cannot be exploited when the default option of 'High-performance order storage' is enabled.

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

The Order Export for WooCommerce plugin stores exported order data insecurely in the web-accessible /wp-content/uploads directory. When the plugin is configured to use 'WordPress posts storage (legacy)', unauthenticated attackers can directly browse this directory and download sensitive order information including customer PII, shipping addresses, and transaction details.

MitigationChange the 'Order data storage' setting from 'WordPress posts storage (legacy)' to 'High-performance order storage' (the default), or update to a patched version when available. Verify the current configuration via WooCommerce > Settings > Advanced > Order Export.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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 Order Export for WooCommerce plugin is installed
    Navigate to Plugins > Instored Plugins in WordPress admin and confirm 'Order Export for WooCommerce' appears in the list. Note the installed version for comparison against any patched releases.
    Affected if Plugin is installed regardless of version - the vulnerability exists when legacy storage is enabled.
  2. Check the Order data storage configuration setting
    Go to WooCommerce > Settings > Advanced > Order Export. Locate the 'Order data storage' dropdown or radio option. Record whether it is set to 'WordPress posts storage (legacy)' or 'High-performance order storage'.
    Affected if The setting is set to 'WordPress posts storage (legacy)' - this is the vulnerable configuration.
  3. Inspect the wp-content/uploads directory for exported files
    Using FTP, file manager, or SSH, list contents of /wp-content/uploads/ (and any dated subdirectories within). Look for files with names suggesting order exports such as export, order, csv, xml, or json files.
    Affected if Export files exist in the web-accessible uploads directory and the storage setting is set to legacy mode.
  4. Confirm files are directly accessible via web browser
    Attempt to access a suspected export file via HTTP/HTTPS URL (e.g., visit yoursite.com/wp-content/uploads/[filename]) in a private browser window without authentication.
    Affected if The export files are reachable without authentication - this confirms the exploit condition.

A user is affected if the Order Export for WooCommerce plugin is installed AND the 'Order data storage' setting is configured to 'WordPress posts storage (legacy)', allowing unauthenticated web access to exported order data.

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

Change the 'Order data storage' setting from 'WordPress posts storage (legacy)' to 'High-performance order storage' (the default), or update to a patched version when available. Verify the current configuration via WooCommerce > Settings > Advanced > Order Export.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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