dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-37113

CRITICAL · 9.8 CVSS v3.1 Published 2024-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Membership Software WishList Member X.This issue affects WishList Member X: from n/a before 3.26.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

An information disclosure vulnerability in WishList Member X allows unauthorized actors to access sensitive data. The flaw exists in versions prior to 3.26.7 and is classified as a critical severity issue (CVSS 9.8).

MitigationUpgrade WishList Member X to version 3.26.7 or later. Conduct a security audit to determine what sensitive information may have been exposed and notify affected users accordingly.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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. Locate WishList Member X installation
    Check your WordPress plugins directory or WordPress admin dashboard under Plugins to find WishList Member X
    Affected if The plugin is installed and version is below 3.26.7
  2. Identify installed version number
    In WordPress admin, go to Plugins > WishList Member X and view the version displayed, or check the main plugin file header for the Version constant
    Affected if Version shown is earlier than 3.26.7 (e.g., 3.26.6, 3.25.x, etc.)
  3. Confirm plugin is active
    Verify the WishList Member X plugin status in WordPress admin under Plugins > Installed Plugins
    Affected if Plugin is active and version is below 3.26.7

You are affected if WishList Member X is installed and the installed version is any version prior to 3.26.7.

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

Upgrade WishList Member X to version 3.26.7 or later. Conduct a security audit to determine what sensitive information may have been exposed and notify affected users accordingly.

Recommended fix High confidence

3.26.7

  1. Backup your WordPress site and database before performing any updates
  2. Update WishList Member X to version 3.26.7 or later through the WordPress admin dashboard or via FTP
  3. Verify the update was successful by checking the plugin version in the WordPress admin plugins section
  4. Clear any caching systems if used to ensure the patched version is fully deployed

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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