dbcve.org
File Uploads Addon For WoocommerceWordPress extension · Imaginate Solutions

CVE-2024-13622

HIGH · 7.5 CVSS v3.1 Published 2025-02-18
Fix available
A fix is available. Upgrade to after 1.7.1 or later.
See remediation →
84/100
Remediation priority · High
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 File Uploads Addon for WooCommerce plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.7.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 uploaded by customers.

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 File Uploads Addon for WooCommerce plugin stores customer-uploaded files in /wp-content/uploads without proper access controls, allowing unauthenticated attackers to directly browse and download sensitive file attachments through the publicly accessible uploads directory.

MitigationRestrict access to the uploads directory via web server configuration (e.g., .htaccess rules to disable directory listing and prevent direct file access) and update to the patched version when 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
File Uploads Addon For WoocommerceWordPress extension
Affected:<= 1.7.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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Imaginate Solutions File Uploads Addon For Woocommerce'. Check the version number displayed under the plugin name. Alternatively, examine the plugin header in /wp-content/plugins/file-uploads-addon-for-woocommerce/file-uploads-addon-for-woocommerce.php for the 'Version' tag.
    Affected if The installed version is 1.7.1 or lower.
  2. Locate the uploads directory
    Check the plugin settings in WordPress admin under WooCommerce > Settings > File Uploads Addon, or examine the plugin code for the upload path configuration. The vulnerability stores files in /wp-content/uploads by default.
    Affected if The plugin stores uploaded files in a publicly accessible directory under /wp-content/uploads.
  3. Verify .htaccess protection exists
    Inspect /wp-content/uploads/.htaccess and check for rules that deny direct file access. Look for directives like 'Deny from all' or rules that prevent direct PHP execution and access.
    Affected if No .htaccess file exists in /wp-content/uploads, or the file lacks access restrictions.
  4. Test directory listing exposure
    Attempt to access https://yourdomain.com/wp-content/uploads/ directly in a browser. If directory listing is enabled, a list of files and folders will be displayed.
    Affected if The uploads directory is publicly browsable and displays a file listing.
  5. Confirm direct file access is unrestricted
    Upload a test file through the plugin if possible, then try to access it directly via its URL (e.g., https://yourdomain.com/wp-content/uploads/2024/filename.ext). The vulnerability allows direct access without authentication.
    Affected if Uploaded files can be downloaded directly without any access controls or authentication.

A user is affected if the plugin version is 1.7.1 or lower AND the uploads directory lacks .htaccess restrictions that prevent direct file access and directory listing.

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 1.7.1
Interim mitigation

Restrict access to the uploads directory via web server configuration (e.g., .htaccess rules to disable directory listing and prevent direct file access) and update to the patched version when available.

Fix this in File Uploads Addon For Woocommerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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