CVE-2024-13640
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 · uneditedThe Print Invoice & Delivery Notes for WooCommerce plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 5.4.1 via the 'wcdn/invoice' directory. This makes it possible for unauthenticated attackers to extract sensitive data stored insecurely in the /wp-content/uploads/wcdn/invoice directory which can contain invoice files if an email attachment setting 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 confidenceThe Print Invoice & Delivery Notes for WooCommerce plugin stores invoice files in a publicly accessible web directory (/wp-content/uploads/wcdn/invoice) without authentication checks. When the email attachment setting is enabled, sensitive invoice documents containing customer PII, order details, and payment information can be extracted by any unauthenticated user who can directly access this directory.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if the plugin is installedCheck your WordPress installation for the 'Print Invoice & Delivery Notes for WooCommerce' plugin in wp-content/plugins/ or via the WordPress admin Plugins page. Note the installed version number.Affected if The plugin is present on the site
-
Check for the vulnerable invoice directoryVerify the existence of /wp-content/uploads/wcdn/invoice/ directory on the web server. Use file manager, FTP, or command line to list this path.Affected if The wcdn/invoice directory exists on the server
-
Test unauthenticated access to invoice filesAttempt to access the directory directly via a web browser without logging in (e.g., visit https://yourdomain.com/wp-content/uploads/wcdn/invoice/). Look for a directory listing or ability to download files.Affected if The directory is publicly accessible and files can be viewed or downloaded without authentication
-
Check if email attachment setting is enabledIn WordPress admin, go to WooCommerce > Settings > Invoice > Email Attachments tab (or similar plugin settings area) and verify if the attachment setting is turned on.Affected if Email attachment functionality is enabled in the plugin settings
You are affected if the plugin is installed, the wcdn/invoice directory exists and is accessible without authentication, and the email attachment setting is enabled, allowing unauthenticated users to download sensitive invoice documents.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the plugin to the latest version immediately. If unable to update, disable the email attachment setting and restrict access to the wcdn/invoice directory via web server configuration (e.g., .htaccess rules to require authentication).
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13640 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-13640 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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