dbcve.org
VulnerabilityAwaiting classification

CVE-2026-10820

HIGH · 8.1 CVSS v3.1 Published 2026-06-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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 Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile & Restrict Content WordPress plugin before 4.16.17 does not verify that the user performing a subscription action owns the targeted subscription, allowing any authenticated user (Subscriber+) to cancel other users' active subscriptions via an Insecure Direct Object Reference.

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 WordPress Paid Membership plugin before version 4.16.17 contains an Insecure Direct Object Reference (IDOR) vulnerability in its subscription management functionality. The plugin fails to verify that the authenticated user owns the targeted subscription before processing cancellation requests. Any user with Subscriber-level access or higher can exploit this to cancel other users' active subscriptions by manipulating subscription IDs in the request.

MitigationUpdate the plugin to version 4.16.17 or later, which implements proper ownership verification for subscription actions. Until updated, monitor subscription cancellation logs for unauthorized activity.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

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

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. Check installed plugin version
    Navigate to WordPress Admin > Plugins > Paid Memberships Pro, or inspect the plugin header in wp-content/plugins/paid-memberships-pro/readme.txt to find the 'Stable tag' version
    Affected if Version is lower than 4.16.17 (e.g., 4.16.16, 4.16.0, etc.) or the version cannot be determined
  2. Verify subscription management is accessible
    Log in as a user with Subscriber role and attempt to access the subscription cancellation endpoint (typically /wp-json/pmpro/v1/subscription or the membership account page with cancel action)
    Affected if Subscriber-level users can access subscription cancellation functionality without ownership verification
  3. Check subscription cancellation capability
    As a Subscriber user, submit a cancellation request with a subscription ID belonging to a different user (modify the subscription_id parameter in the request)
    Affected if The cancellation request succeeds or returns a non-403 response for a subscription the user does not own
  4. Review subscription cancellation logs
    Check WordPress debug logs, plugin activity logs, or database records in the pmpro_membership_orders table for cancellation events where user_id does not match the subscription owner
    Affected if Cancellation records exist where the acting user_id differs from the subscription's user_id
  5. Confirm user role configuration
    Navigate to WordPress Admin > Memberships > Settings > Advanced > Role Settings and verify if the Subscriber role has permission to manage subscriptions
    Affected if Subscriber role is granted subscription cancellation or management permissions

Your environment is affected if the plugin version is below 4.16.17 AND Subscriber-level users can access and successfully cancel subscriptions they do not own via direct ID manipulation.

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 the plugin to version 4.16.17 or later, which implements proper ownership verification for subscription actions. Until updated, monitor subscription cancellation logs for unauthorized activity.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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