dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-24625

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/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
Missing Authorization vulnerability in Imaginate Solutions File Uploads Addon for WooCommerce woo-addon-uploads allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects File Uploads Addon for WooCommerce: from n/a through <= 1.7.3.

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 Missing Authorization vulnerability in the Imaginate Solutions File Uploads Addon for WooCommerce (versions through 1.7.3). The plugin fails to properly enforce authorization checks on file upload functionality, allowing attackers to exploit incorrectly configured access control security levels. This likely enables unauthorized users to upload files or access uploaded content without proper authentication/authorization permissions.

MitigationImplement proper authorization checks on all file upload endpoints and ensure WordPress capability checks are enforced before allowing any upload or access operations. Update to the latest plugin version if a patch is available, and audit existing file access controls.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Imaginate Solutions File Uploads Addon for WooCommerce' or check the plugin's main PHP file header for the Version comment. Alternatively, examine the plugin directory /wp-content/plugins/imaginate-file-uploads/ for the main plugin file and read the version defined in the plugin metadata.
    Affected if The plugin is installed and the version is 1.7.3 or any lower version through 1.0.0 (all versions through 1.7.3 are affected)
  2. Verify file upload functionality is enabled
    Check the plugin settings in WordPress admin under WooCommerce > File Uploads or a similar plugin settings page. Look for any toggle or setting that enables/disables the upload functionality. Also examine the plugin's main class file for any upload-related action/filter hooks (e.g., 'init' handlers for file upload processing).
    Affected if The file upload feature is active/enabled in the plugin configuration
  3. Inspect upload endpoint access controls
    Examine the plugin's PHP files for upload handler functions. Look for missing 'current_user_can()' checks or 'wp_verify_nonce()' calls before processing file uploads. Check files like class-imaginate-upload.php or similar upload handler classes. Search for 'add_action' hooks handling 'wp_ajax_' or 'wp_ajax_nopriv_' prefixes related to upload actions.
    Affected if The upload endpoint handlers lack proper capability checks or nonce validation (e.g., no current_user_can() call before file processing)
  4. Check access control security level configuration
    Review the plugin settings for any 'Access Control', 'Security Level', or 'Permission' settings. Examine the database option values (in wp_options table) for any plugin-specific settings related to who can upload or access files. Look for misconfigured 'roles' or 'capabilities' settings that may allow lower-privileged users or unauthenticated users.
    Affected if The access control or security level setting is configured to allow unauthenticated users or users without proper WooCommerce/capability permissions to access upload functionality

Your environment is affected if the Imaginate Solutions File Uploads Addon for WooCommerce plugin (versions through 1.7.3) is installed with the upload feature enabled and the authorization checks are missing or misconfigured to allow unauthorized access.

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

Implement proper authorization checks on all file upload endpoints and ensure WordPress capability checks are enforced before allowing any upload or access operations. Update to the latest plugin version if a patch is available, and audit existing file access controls.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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