dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-1869

MEDIUM · 6.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 →
74/100
Remediation priority · Elevated
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
The User Registration & Membership – Free & Paid Memberships, Subscriptions, Content Restriction, User Profile, Custom User Registration & Login Builder plugin for WordPress is vulnerable to unauthorized modification of data due to missing validation checks in the confirm_payment() function in all versions up to, and including, 5.2.0. This makes it possible for unauthenticated attackers to bypass payment processing and activate paid memberships.

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

This WordPress membership plugin has a broken access control vulnerability in the confirm_payment() function. The function lacks proper validation of payment status and user authorization, allowing unauthenticated attackers to manipulate the payment confirmation process and activate paid memberships without actually completing payment.

MitigationUpdate the plugin to version 5.2.1 or later once available. Alternatively, disable the plugin or restrict access to payment-related endpoints at the web server level until a patch is applied.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 WordPress membership plugin
    In the WordPress admin dashboard, navigate to Plugins > Installed Plugins and look for any membership-related plugin (e.g., membership, subscription, paid content access). Note the exact plugin name and file path.
    Affected if A WordPress membership plugin is installed and the confirm_payment() function exists in the plugin code.
  2. Determine plugin version
    In the plugin list, click on the plugin to view its details, or inspect the plugin's main PHP file for a version constant (often defined as 'VERSION' or 'PLUGIN_VERSION'). Compare this version to the patched version 5.2.1.
    Affected if The installed plugin version is earlier than 5.2.1, as versions prior to this release contain the vulnerable confirm_payment() function.
  3. Locate the confirm_payment function
    Using a file manager or code editor, search the plugin directory for the function 'function confirm_payment()' or 'function confirm_payment(' to confirm the vulnerable function exists.
    Affected if The function confirm_payment() is present in the plugin files, indicating the potentially vulnerable code path exists.
  4. Verify payment endpoint accessibility
    Check if the payment confirmation URL endpoint (commonly /confirm-payment/ or similar) is accessible without authentication by attempting to access it or reviewing the plugin's routing configuration for unauthenticated access patterns.
    Affected if The payment confirmation endpoint can be accessed without authentication or payment status validation, confirming the broken access control exists.

A user is affected if they have a WordPress membership plugin with a confirm_payment() function that is version earlier than 5.2.1 and exposes payment confirmation logic without requiring authentication or payment verification.

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 the plugin to version 5.2.1 or later once available. Alternatively, disable the plugin or restrict access to payment-related endpoints at the web server level until a patch is applied.

Recommended fix Moderate confidence

Latest version after 5.2.0 (check wordpress.org for current stable release)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Find 'User Registration & Membership' plugin
  4. 4. Check the current version number (should be 5.2.0 or below if vulnerable)
  5. 5. If an update is available, click 'Update Now' to install the latest version
  6. 6. Alternatively, download the latest version from wordpress.org/plugins/user-registration and upload via Plugins > Add New > Upload Plugin
  7. 7. After update, verify the confirm_payment() function has been patched by checking plugin changelog or release notes

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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