dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-66107

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-21
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
Missing Authorization vulnerability in Scott Paterson Subscriptions & Memberships for PayPal subscriptions-memberships-for-paypal allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Subscriptions & Memberships for PayPal: from n/a through <= 1.1.7.

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

This is a Missing Authorization (Broken Access Control) vulnerability in the Subscriptions & Memberships for PayPal WordPress plugin. The vulnerability allows attackers to bypass access control checks and access functionality or data that should require proper authorization, likely due to missing capability checks or nonce validations on subscription management endpoints.

MitigationImplement proper authorization checks (using current_user_can() and nonces) on all sensitive functions that handle subscription data, membership access, or user-specific operations. Review all AJAX endpoints and front-facing forms for missing authorization controls.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Locate the plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for a folder containing 'paypal' and 'subscription' or 'membership' in the name, or search for files containing 'PayPal' plugin headers using grep -r 'Plugin Name:.*PayPal.*Subscription' wp-content/plugins/
    Affected if The plugin folder 'paypal-subscriptions-memberships' or similar is found in the plugins directory
  2. Identify the installed version
    Read the main plugin file (usually the primary PHP file in the plugin folder) and look for the 'Version:' header in the plugin comment block, or check the WordPress admin Plugins page
    Affected if The plugin is installed and a Version header exists (without a specific fix version known, any installed version should be treated as potentially vulnerable)
  3. Check for subscription management AJAX endpoints
    Search the plugin directory for AJAX action registrations: grep -r 'add_action.*wp_ajax' wp-content/plugins/[plugin-folder] | grep -i 'subscription\|member\|user'
    Affected if AJAX endpoints related to subscriptions or membership are registered
  4. Verify authorization controls on sensitive functions
    Search the plugin PHP files for sensitive functions (like those handling subscription data, user access, or membership content) and check if they include current_user_can() calls: grep -rn 'function.*subscription\|function.*member' wp-content/plugins/[plugin-folder]/*.php and grep -n 'current_user_can' wp-content/plugins/[plugin-folder]/*.php
    Affected if Sensitive subscription or membership functions exist but lack current_user_can() capability checks nearby

The environment is affected if the PayPal Subscriptions & Memberships plugin is installed and its sensitive endpoints lack proper capability checks (current_user_can()) or nonce validations, allowing unauthenticated or unauthorized access to subscription management functions.

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

Implement proper authorization checks (using current_user_can() and nonces) on all sensitive functions that handle subscription data, membership access, or user-specific operations. Review all AJAX endpoints and front-facing forms for missing authorization controls.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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