CVE-2025-13538
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 Listing plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.0.5. This is due to the 'findall_listing_user_registration_additional_params' function not restricting what user roles a user can register with. This makes it possible for unauthenticated attackers to supply the 'administrator' role during registration and gain administrator access to the site. Note: The vulnerability can only be exploited if the FindAll Membership plugin is also activated, because user registration is in that plugin.
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 Listing WordPress plugin has a privilege escalation vulnerability in versions up to 1.0.5. The vulnerable function `findall_listing_user_registration_additional_params` does not validate or restrict the user role parameter during registration, allowing unauthenticated attackers to specify the 'administrator' role and gain full administrative access to the WordPress site. Exploitation requires the FindAll Membership plugin to be active, as it handles the user registration functionality.
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 FindAll Listing plugin versionNavigate to Plugins > Installed Plugins in WordPress admin, locate FindAll Listing, and note the version number. Alternatively, inspect the plugin main file header or use: wp plugin list --name=findall-listingAffected if Version is 1.0.5 or lower (versions up to 1.0.5 are affected)
-
Check if FindAll Membership plugin is activeNavigate to Plugins > Installed Plugins in WordPress admin, locate FindAll Membership, and verify its status. Alternatively, use: wp plugin list --status=active --name=findall-membershipAffected if FindAll Membership plugin is active (exploitation requires this plugin as it contains the user registration functionality)
-
Verify WordPress user registration is enabledGo to WordPress admin > Settings > General > Membership: ensure 'Anyone can register' is checked. Alternatively, check the 'users_can_register' option in wp-options via: wp option get users_can_registerAffected if User registration is enabled on the WordPress site (the vulnerability is exploited during the registration process)
-
Inspect the findall_listing_user_registration_additional_params functionExamine the FindAll Listing plugin source code, specifically the function findall_listing_user_registration_additional_params in the main plugin file. Look for whether the user role parameter is validated or restricted before being passed to wp_create_user or related functions.Affected if The function does not validate or restrict the role parameter, allowing arbitrary role assignment including 'administrator'
You are affected if FindAll Listing plugin version is 1.0.5 or lower, FindAll Membership plugin is active, and WordPress user registration is enabled, allowing unauthenticated privilege escalation to administrator.
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 · scopedImmediately update the FindAll Listing plugin to the latest version once available. Until then, disable the FindAll Membership plugin to prevent user registration, or remove the plugins entirely if not needed. Monitor for any unauthorized administrator accounts created on the site.
FindAll Listing plugin version 1.0.6 or later (and FindAll Membership plugin latest version)
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate the FindAll Listing plugin
- 4. If an update is available, click 'Update Now' to install the latest version
- 5. Also check and update the FindAll Membership plugin to its latest version
- 6. After updating, verify that the privilege escalation vulnerability is resolved by confirming user registration no longer allows arbitrary role assignment
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13538 — 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-13538 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