Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-56013

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 8 weeks old

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 Insecure Direct Object References (IDOR) in License Manager for WooCommerce <= 3.0.15 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 · moderate confidence

Unauthenticated IDOR vulnerability in License Manager for WooCommerce plugin versions 3.0.15 and below allows attackers to access or modify license data without proper authorization due to missing access control validation on object references.

MitigationUpdate License Manager for WooCommerce to the latest version beyond 3.0.15 to include patched access control mechanisms.

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
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

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 plugin installation
    Check if the License Manager for WooCommerce plugin is present in the WordPress plugins directory at wp-content/plugins/license-manager-for-woocommerce/ or view it in the WordPress admin under Plugins
    Affected if Plugin is installed regardless of active state
  2. Identify the installed version
    Open the main plugin file (typically license-manager-for-woocommerce.php) and locate the version string in the plugin header comment, or check the version column in WordPress admin Plugins page
    Affected if Version displayed is 3.0.15 or any version number lower than 3.0.15
  3. Confirm the plugin is active
    Check the Plugins list in WordPress admin or query the wp_options table for option_name = 'active_plugins' to see if the plugin is enabled
    Affected if Plugin is active; unauthenticated IDOR can be exploited without user authentication
  4. Verify the IDOR endpoint exists
    Inspect plugin files for AJAX handlers or REST API endpoints that handle license object references (such as license keys, license IDs, or user IDs in request parameters) without checking ownership or authorization
    Affected if Any endpoint processes object references (e.g., license_id, key_id, user_id) without validate_ownership() or current_user_can() checks

Your environment is affected if License Manager for WooCommerce is installed with version 3.0.15 or lower and the plugin is active, exposing license data manipulation via unauthenticated requests to endpoints lacking proper ownership validation.

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

Update License Manager for WooCommerce to the latest version beyond 3.0.15 to include patched access control mechanisms.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-56013 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