dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-49061

HIGH · 7.5 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Unauthenticated Arbitrary File Download in WPC Product Options for WooCommerce <= 3.2.1 versions.

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 WPC Product Options for WooCommerce plugin versions 3.2.1 and below contains an unauthenticated arbitrary file download vulnerability. Attackers can exploit this to download sensitive files from the server by manipulating file path parameters in the download functionality, without requiring any authentication credentials.

MitigationUpgrade to WPC Product Options for WooCommerce version 3.2.2 or later. As an immediate workaround, disable the plugin or restrict access to the affected download endpoint at the web server level until the patch can be applied.

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
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. Locate the WPC Product Options plugin directory
    Check your WordPress plugins folder (commonly wp-content/plugins/) for a directory named 'woo-product-options' or similar WPC-related folder
    Affected if The plugin directory exists in your WordPress installation
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually named index.php or the primary plugin file) and look for the 'Version' header comment, or check the readme.txt file for the version number
    Affected if The version number returned is 3.2.1 or lower
  3. Check the WordPress admin plugin list
    Log into the WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate 'WPC Product Options for WooCommerce' and note the version displayed
    Affected if The version shown is 3.2.1 or lower
  4. Inspect the download functionality endpoint
    Search the plugin files for functions handling file downloads (look for terms like 'download', 'file_get_contents', 'readfile', or 'fopen' with user-controlled parameters)
    Affected if The plugin contains a download handler that accepts file path parameters without proper validation
  5. Verify unauthenticated access to download features
    Test the suspected download endpoint without providing any authentication credentials (cookies, tokens, or login session)
    Affected if The endpoint responds and allows file retrieval without authentication

If the WPC Product Options for WooCommerce plugin is installed at version 3.2.1 or below and the download functionality is accessible without authentication, the environment is affected by this CVE.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to WPC Product Options for WooCommerce version 3.2.2 or later. As an immediate workaround, disable the plugin or restrict access to the affected download endpoint at the web server level until the patch can be applied.

Recommended fix High confidence

WPC Product Options for WooCommerce version 3.2.2 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'WPC Product Options for WooCommerce' in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the latest version from the WordPress plugin repository or WPC official site and upload it via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin is active and functioning correctly

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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