dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-34886

HIGH · 7.5 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Unauthenticated Broken Access Control in Simple Membership <= 4.7.1 versions.

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

Unauthenticated Broken Access Control vulnerability in Simple Membership plugin for WordPress versions 4.7.1 and below allows remote attackers to access resources or perform actions without proper authentication. The CVSS 7.5 score indicates a network-exploitable, low-complexity attack requiring no privileges or user interaction.

MitigationUpdate Simple Membership plugin to a version newer than 4.7.1. If no patched version is available, disable the plugin until a fix is released or implement additional access control measures at the web server level.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Verify Simple Membership plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins. Look for 'Simple Membership' in the plugin list.
    Affected if The Simple Membership plugin appears in the installed plugins list.
  2. Check the installed version number
    In the installed plugins list, locate Simple Membership. The version number is displayed directly below the plugin name.
    Affected if A version number is visible next to the Simple Membership plugin entry.
  3. Compare version against affected range
    Compare the installed version to the affected range. Versions 4.7.1 and below (such as 4.7.1, 4.7.0, 4.6.x, etc.) are within the affected range.
    Affected if The installed version is 4.7.1 or any version lower than 4.7.1.
  4. Confirm plugin is activated
    In WordPress admin > Plugins, verify the Simple Membership plugin shows as 'Active'. Check the frontend to confirm membership-related pages or endpoints are publicly accessible.
    Affected if The plugin is activated and membership functionality is publicly accessible without authentication.

If Simple Membership plugin version 4.7.1 or below is installed and active, the environment is affected by this unauthenticated broken access control vulnerability.

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 Simple Membership plugin to a version newer than 4.7.1. If no patched version is available, disable the plugin until a fix is released or implement additional access control measures at the web server level.

Recommended fix Moderate confidence

Simple Membership latest version (likely 4.7.2 or higher - check WordPress plugin repository for current stable release)

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. 3. Find the Simple Membership plugin
  4. 4. Check the current installed version (should be <= 4.7.1 based on CVE description)
  5. 5. If an update is available, click 'Update Now' to upgrade to the latest version
  6. 6. Verify the update completed successfully
  7. 7. Test that membership functionality still works correctly after the update

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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