CVE-2025-58000
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 · uneditedMissing Authorization vulnerability in memberful Memberful - Membership Plugin memberful-wp allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Memberful - Membership Plugin: from n/a through <= 1.75.0.
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 confidenceMissing Authorization vulnerability in the Memberful WordPress plugin (memberful-wp) allows unauthenticated or unauthorized users to access functionality that should be restricted by Access Control Lists (ACLs). The plugin fails to properly validate user permissions before executing certain actions, enabling privilege escalation or unauthorized access to membership features.
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
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Memberful plugin installationIn WordPress admin, go to Plugins > Installed Plugins and look for 'Memberful' or 'memberful-wp' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named 'memberful' or 'memberful-wp'.Affected if The plugin is not found in the plugins list or directory.
-
Identify the installed versionIn WordPress admin, click on the Memberful plugin to view its details, or open the main plugin file (usually memberful.php) in a code editor and look for a 'Version:' comment in the file header. You can also check /wp-content/plugins/memberful-wp/readme.txt for the version number.Affected if The version cannot be determined or is older than the vendor patched version.
-
Test access control on membership endpointsUsing a tool like Burp Suite or curl, attempt to access common Memberful API endpoints without authentication (e.g., /?memberful_api_action=..., /wp-json/memberful/... endpoints). Also test accessing wp-admin/admin-ajax.php?action=memberful_... without being logged in.Affected if Requests return successful responses or membership data without requiring valid authentication or authorization.
-
Review access logs for unauthorized membership actionsExamine WordPress debug logs (wp-content/debug.log if enabled), server access logs, and Memberful activity logs for repeated requests to ACL-protected actions from unauthenticated IPs or unauthorized user IDs.Affected if Logs show membership data, user role changes, or protected feature access from unrecognized or anonymous sources.
You are affected if the Memberful plugin is installed and either the version is older than the patched release OR unauthorized access to membership functionality is possible without proper authentication.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate Memberful plugin to the latest version as soon as a patch is released by the vendor. Until then, restrict wp-admin access to trusted users only and monitor for suspicious activity.
- Consultation1.0 h
- Implementation0.5 h
- Testing1.0 h
- Review / QA0.5 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58000 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-58000 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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