dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-56061

HIGH · 7.5 CVSS v3.1 Published 2026-06-26
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 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 Broken Access Control in Subscriptions for WooCommerce <= 1.9.5 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

Unauthenticated broken access control vulnerability in the Subscriptions for WooCommerce plugin versions 1.9.5 and earlier allows unauthenticated attackers to access subscription management functionality they should not have access to, potentially enabling unauthorized subscription modifications or data exposure.

MitigationUpdate Subscriptions for WooCommerce to the latest patched version, or if no update is available, implement custom access control logic to validate user authorization before allowing subscription operations.

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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Verify Subscriptions for WooCommerce plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Subscriptions for WooCommerce' or check the plugin files in /wp-content/plugins/
    Affected if The plugin is not installed or not present on the system
  2. Determine the installed plugin version
    Check the plugin header in the main plugin file (usually subscriptions-for-woocommerce.php) for the Version field, or view it in the WordPress plugin admin page
    Affected if The version is 1.9.5 or any earlier version
  3. Confirm subscription management endpoints are accessible
    Test accessing WooCommerce subscription-related REST API endpoints or admin pages without authenticating (e.g., using a browser incognito window or curl without auth tokens)
    Affected if Unauthenticated requests return subscription data or allow subscription operations without being rejected with 401/403 errors

A user is affected if the Subscriptions for WooCommerce plugin version is 1.9.5 or earlier and subscription management functionality is accessible without authentication.

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

Update Subscriptions for WooCommerce to the latest patched version, or if no update is available, implement custom access control logic to validate user authorization before allowing subscription operations.

Recommended fix Moderate confidence

Update to the latest version of Subscriptions for WooCommerce (version 1.9.6 or newer)

  1. 1. Backup your WordPress database and files before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Find the 'Subscriptions for WooCommerce' plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, you can download the latest version from the WordPress Plugin Repository and upload it manually
  6. 6. After updating, verify the plugin is working correctly and test subscription functionality

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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