dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-1926

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-18
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
The Subscriptions for WooCommerce plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the `wps_sfw_admin_cancel_susbcription()` function in all versions up to, and including, 1.9.2. This is due to the function being hooked to the `init` action without any authentication or authorization checks, and only performing a non-empty check on the nonce parameter without actually validating it via `wp_verify_nonce()`. This makes it possible for unauthenticated attackers to cancel any active WooCommerce subscription by sending a crafted GET request with an arbitrary nonce value via the `wps_subscription_id` parameter.

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 Subscriptions for WooCommerce plugin has a missing capability check on the wps_sfw_admin_cancel_susbcription() function hooked to WordPress's init action. The function only checks if the nonce parameter is non-empty without actually validating it via wp_verify_nonce(), allowing unauthenticated attackers to cancel any active WooCommerce subscription by sending a crafted GET request with arbitrary nonce value via the wps_subscription_id parameter.

MitigationUpgrade to version 1.9.3 or later which adds proper nonce verification and capability checks; until patched, consider disabling the plugin or blocking the vulnerable endpoint via WAF.

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 if Subscriptions for WooCommerce is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'subscriptions-for-woocommerce' or similar, or list active plugins via WP-CLI: wp plugin list --status=active --field=name
    Affected if The plugin is present in the plugins directory regardless of active status (but must be active to be exploitable)
  2. Check the installed plugin version
    Open the plugin's main PHP file (usually in the plugin root folder, e.g., subscriptions-for-woocommerce.php) and look for the 'Version' header in the file comment block, or run: wp plugin get subscriptions-for-woocommerce --field=version
    Affected if The version is below 1.9.3 (the summary indicates 1.9.3 adds proper nonce verification)
  3. Confirm the plugin is active
    Run: wp plugin status subscriptions-for-woocommerce (or check via WordPress admin Plugins page)
    Affected if The plugin is active - the vulnerable function is hooked to WordPress init action and runs on every request when active
  4. Verify the vulnerable function exists
    Search the plugin source code for the function 'wps_sfw_admin_cancel_susbcription' (note the typo) - this function should be hooked to 'init' action
    Affected if The function exists and is hooked to init (this is the case in unpatched versions); no special configuration is required for exploitation

The environment is affected if the Subscriptions for WooCommerce plugin is active with a version prior to 1.9.3, as the vulnerable function runs on every request due to the init hook with only a non-empty nonce check.

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 version 1.9.3 or later which adds proper nonce verification and capability checks; until patched, consider disabling the plugin or blocking the vulnerable endpoint via WAF.

Recommended fix Moderate confidence

Latest version (likely 1.9.3 or higher)

  1. 1. Update the Subscriptions for WooCommerce plugin to the latest available version from the WordPress plugin repository
  2. 2. After updating, verify that the `wps_sfw_admin_cancel_subscription()` function now includes proper capability checks using `current_user_can()` or similar WordPress authorization functions
  3. 3. Verify that nonce verification is now properly implemented with `wp_verify_nonce()` rather than just empty checks
  4. 4. Test that WooCommerce subscription cancellation requires appropriate admin privileges
  5. 5. Monitor WordPress audit logs to confirm the authorization controls are functioning

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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