Information ExposureWeakness · CWE-200

CVE-2024-12434

MEDIUM · 5.3 CVSS v3.1 Published 2025-02-26
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 SureMembers plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.10.6 via the REST API. This makes it possible for unauthenticated attackers to extract sensitive data including restricted content.

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 SureMembers WordPress plugin versions up to 1.10.6 has a broken access control vulnerability in its REST API that allows unauthenticated attackers to bypass authorization checks and extract sensitive membership-restricted content without any credentials.

MitigationUpdate the SureMembers plugin to version 1.10.7 or later which contains the patched REST API authorization logic.

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. Confirm SureMembers plugin is installed
    Log into WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'SureMembers' in the list of active plugins.
    Affected if The plugin is installed and active
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins. Click on 'SureMembers' to view the plugin details, or inspect the plugin header in /wp-content/plugins/suremembers/readme.txt to find the Version field.
    Affected if Version is 1.10.6 or lower (any version up to and including 1.10.6)
  3. Verify REST API authorization bypass vulnerability
    Send a GET request to the SureMembers REST API endpoint (typically /wp-json/suremembers/v1/ or similar membership-related endpoints) WITHOUT providing any authentication credentials. Inspect the HTTP response code and body.
    Affected if The API returns 200 OK with membership-restricted content or sensitive data without requiring authentication tokens
  4. Test access to restricted content
    Attempt to access a page or post that is configured as member-only in SureMembers settings using an incognito browser window (no logged-in user). Check if the full restricted content is displayed.
    Affected if Protected content is fully visible to unauthenticated users who are not logged in

User is affected if SureMembers plugin version is 1.10.6 or lower AND the REST API endpoints respond to unauthenticated requests with membership-restricted data.

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 SureMembers plugin to version 1.10.7 or later which contains the patched REST API authorization logic.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12434 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-2024-12434 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