CVE-2025-12778
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 Ultimate Member Widgets for Elementor – WordPress User Directory plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the handle_filter_users function in all versions up to, and including, 2.3. This makes it possible for unauthenticated attackers to extract partial metadata of all WordPress users, including their first name, last name and email addresses.
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 Ultimate Member Widgets for Elementor plugin has a broken access control vulnerability in the handle_filter_users function. This function, used for filtering WordPress users in the Elementor widgets, lacks a capability check, allowing any unauthenticated request to query and retrieve sensitive user metadata including first names, last names, and email addresses.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin installationCheck if the Ultimate Member Widgets for Elementor plugin is installed in your WordPress environment. Look in wp-content/plugins/ for a folder containing 'ultimate-member' and 'elementor' in the name, or check via WordPress admin under Plugins.Affected if The plugin is installed
-
Check installed versionLocate the main plugin file (usually ultimate-member-widgets-for-elementor.php or similar) and read the Version header in the plugin comments. Alternatively, check the version displayed in WordPress admin under Plugins.Affected if Version is less than 2.4
-
Verify unauthenticated access to filter functionTest if the AJAX endpoint used by handle_filter_users is reachable without authentication. This typically involves making a request to wp-admin/admin-ajax.php with action=um_elementor_filter_users (or similar) while logged out. Use a tool like curl: curl -X POST http://your-site.com/wp-admin/admin-ajax.php -d 'action=um_elementor_filter_users' -d 'filter_param=test'Affected if The request returns user data (first names, last names, email addresses) without requiring login
-
Inspect function code for capability checkIf you have file access, locate the handle_filter_users function in the plugin source code. Check if it contains a current_user_can() call or similar capability verification at the beginning of the function.Affected if No capability check (such as current_user_can('list_users')) is present in the function
You are affected if the Ultimate Member Widgets for Elementor plugin is installed with a version earlier than 2.4 and its user filtering function is accessible to unauthenticated visitors.
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 the plugin to version 2.4 or later which includes the missing capability check, or implement a proper capability verification (current_user_can('list_users') or similar) on the handle_filter_users function.
- 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-12778 — 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-12778 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