dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-12093

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-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 Simple Membership plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 4.7.5. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to deactivate arbitrary member accounts by forging a charge.refunded webhook event containing a victim's subscription ID, setting the target member's account_state to 'inactive' and triggering cancellation hooks, transaction-record status changes, and cancellation notification emails. This vulnerability is exploitable only on installations where no Stripe webhook signing secret has been configured, which is the default out-of-the-box state; sites that have configured the stripe-webhook-signing-secret option are routed to the properly verified HMAC path and are not affected.

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 Simple Membership WordPress plugin up to version 4.7.5 lacks proper authorization checks on Stripe webhook handling, allowing unauthenticated attackers to deactivate member accounts by forging charge.refunded events with arbitrary subscription IDs. This only affects installations where the stripe-webhook-signing-secret option remains unconfigured (the default state).

MitigationConfigure a Stripe webhook signing secret in the plugin settings to enable HMAC verification, or update to a patched version when available.

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 Simple Membership plugin version
    Locate the Simple Membership plugin in wp-content/plugins/ and read the main plugin file header for the Version field, or query the database: SELECT option_value FROM wp_options WHERE option_name = 'swpm_version' OR check plugin files directly
    Affected if version is 4.7.5 or lower
  2. Check if Stripe webhook signing secret is configured
    Query the WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'stripe-webhook-signing-secret'
    Affected if the option is empty, missing, or contains no value (default unconfigured state)
  3. Verify Stripe webhook processing is active
    Check if Stripe webhook functionality is enabled: look for option like 'enable-stripe-webhook' or similar in wp_options table, or inspect if the plugin processes Stripe webhooks
    Affected if webhook handling is enabled without the signing secret being set

You are affected if the Simple Membership plugin version is 4.7.5 or lower AND the stripe-webhook-signing-secret option remains unconfigured (empty), allowing unauthenticated webhook requests to trigger account deactivation.

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

Configure a Stripe webhook signing secret in the plugin settings to enable HMAC verification, or update to a patched version when available.

Recommended fix Moderate confidence
  1. 1. Log in to the WordPress admin dashboard.
  2. 2. Navigate to the Simple Membership plugin settings.
  3. 3. Locate the Stripe settings section.
  4. 4. Find the 'stripe-webhook-signing-secret' option (or similar option for configuring Stripe webhook verification).
  5. 5. Configure a valid Stripe webhook signing secret value. This can be obtained from the Stripe dashboard under Webhooks settings for your account.
  6. 6. Save the plugin settings.
  7. 7. Verify that the webhook signing secret is properly saved and the site is now using the HMAC verification path for Stripe webhooks.

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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