Order Attachments For WoocommerceWordPress extension · Directsoftware
CVE-2024-13638
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 Order Attachments for WooCommerce plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.5.1 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 file attachments added to orders.
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 Order Attachments for WooCommerce plugin stores order file attachments in the WordPress uploads directory (/wp-content/uploads) without proper access controls. This allows unauthenticated attackers to directly access and download sensitive order attachments by traversing the uploads directory, exposing customer data and any documents uploaded to orders.
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
Order Attachments For WoocommerceWordPress extension
<= 2.5.1CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/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.
-
Verify the plugin is installedCheck WordPress plugin directory for 'Order Attachments For Woocommerce' or 'directsoftware-order-attachments-for-woocommerce' folder in /wp-content/plugins/Affected if The plugin folder exists in the plugins directory
-
Determine the installed plugin versionOpen the main plugin file (e.g., order-attachments-for-woocommerce.php) and look for the version comment/header, or check in WordPress admin under Plugins > Installed PluginsAffected if Version is 2.5.1 or lower
-
Confirm uploads directory is being usedCheck /wp-content/uploads/ for subdirectories containing order attachments (often named like 'order-attachments' or similar)Affected if Order attachment folders exist in the uploads directory
-
Test direct file accessAttempt to access an uploaded attachment directly via browser (e.g., visit a known attachment URL path under /wp-content/uploads/) without authenticationAffected if Files are directly accessible and downloadable without login
-
Check for access control on uploads directoryInspect the .htaccess file (if Apache) or nginx config for the uploads folder to see if direct access is blockedAffected if No .htaccess or web server rule blocks unauthenticated access to the uploads directory
User is affected if the plugin version is 2.5.1 or lower AND order attachments are stored in /wp-content/uploads AND direct browser access to those files is not restricted by web server configuration.
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.
dbcve · scopedUpdate the plugin to the latest version if available; otherwise, implement web server access controls (e.g., .htaccess rules) to block direct access to the uploads directory, or move sensitive attachments outside the web root with authenticated access only.
Order Attachments for WooCommerce version 2.5.2 or later
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate 'Order Attachments for WooCommerce' in the plugin list
- 4. If an update is available, click 'Update Now' to install the latest version
- 5. Verify the update completed successfully
- 6. Test order attachment functionality to ensure the plugin still works correctly after updating
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Order Attachments For Woocommerce
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13638 — 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-13638 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