CVE-2025-13539
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 · uneditedThe FindAll Membership plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 1.0.4. This is due to the plugin not properly logging in a user with the data that was previously verified through the 'findall_membership_check_facebook_user' and the 'findall_membership_check_google_user' functions. This makes it possible for unauthenticated attackers to log in as administrative users, as long as they have an existing account on the site which can easily be created by default through the temp user functionality, and access to the administrative user's email.
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 confidenceThe FindAll Membership plugin for WordPress has a critical authentication bypass in versions up to 1.0.4. The 'findall_membership_check_facebook_user' and 'findall_membership_check_google_user' functions improperly handle verified user data, failing to establish a secure logged-in session. This allows unauthenticated attackers to authenticate as any administrative user if they have an account (which can be created via the default temp user functionality) and know the admin's email address.
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 checksWork through these to decide whether this CVE applies to you.
-
Check the installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and look for 'FindAll Membership' in the list. The version number is displayed below the plugin name. Alternatively, inspect the plugin file header in wp-content/plugins/findall-membership/Affected if The version is 1.0.4 or lower (any version up to and including 1.0.4)
-
Confirm the plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and verify that FindAll Membership shows as 'Active'Affected if The plugin is active and vulnerable (deactivated plugins cannot be exploited)
-
Check if temp user functionality is enabledIn WordPress admin, navigate to the FindAll Membership plugin settings. Look for options related to 'temp user', 'temporary user', or 'user registration' that are enabled by default. Check the plugin configuration page for any toggle labeled 'Enable Temp User' or similar.Affected if The temp user functionality is enabled (this feature allows attacker to create an account)
-
Audit for unauthorized admin accountsIn WordPress admin, go to Users > All Users. Review the list of users with 'Administrator' role. Look for any accounts that were not created intentionally, especially accounts created around the same time the plugin was activated or accounts with unfamiliar email addresses.Affected if There are admin accounts that were not created by legitimate administrators, or admin accounts exist alongside temp user accounts
-
Verify vulnerable functions exist in plugin codeIf you have file system access, locate the plugin directory (wp-content/plugins/findall-membership/) and search for the functions 'findall_membership_check_facebook_user' and 'findall_membership_check_google_user' in the PHP files. These functions handle the flawed authentication logic.Affected if These functions are present in the plugin code (indicating the vulnerable authentication logic exists)
A user is affected if the FindAll Membership plugin version is 1.0.4 or lower AND the plugin is active AND either the temp user feature is enabled or unauthorized admin accounts exist in the system.
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.
dbcve · scopedUpgrade to version 1.0.5 or later immediately. Also disable the temp user functionality and audit for unauthorized admin accounts created through this feature.
Latest version provided by the plugin developer (version higher than 1.0.4)
- 1. Contact the plugin developer (ThemeForest author) to obtain the patched version of the FindAll Membership plugin
- 2. Verify the latest available version from the ThemeForest product page or WordPress admin panel
- 3. Update the plugin to the latest version provided by the developer
- 4. After updating, test the Facebook and Google login functionality to confirm the authentication fix works correctly
- 5. Ensure any temporary user accounts created through the temp user functionality are reviewed and removed if unnecessary
- 6. Consider enabling additional security measures such as two-factor authentication for administrative accounts
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13539 — 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-13539 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