CVE-2025-11168
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 Mementor Core plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 2.2.5. This is due to plugin not properly handling the user switch back function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to elevate their privileges by accessing an administrator account through the switch back functionality.
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 Mementor Core WordPress plugin has a privilege escalation vulnerability in versions up to 2.2.5. The plugin's user switch back function lacks proper authorization validation, allowing authenticated users with Subscriber-level permissions to improperly switch back to an administrator account and gain elevated privileges.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Verify Mementor Core plugin is installedAccess WordPress admin panel, go to Plugins > Installed Plugins, and search for 'Mementor Core' or examine the plugin directory /wp-content/plugins/ for a mementor-core folderAffected if The Mementor Core plugin is present in the WordPress installation
-
Check installed plugin versionIn WordPress admin, view the plugin details page for Mementor Core to see the version number, or read the main plugin PHP file header for the Version fieldAffected if The installed version is 2.2.5 or lower (any version up to and including 2.2.5)
-
Confirm user switching functionality is activeCheck plugin settings or codebase for the user switch back feature - look for any wp_ajax hooks related to user switching, or inspect if the plugin exposes user_switch_back or similar actions to frontendAffected if The user switching feature is enabled and accessible to authenticated users
-
Identify subscriber-level user accountsNavigate to WordPress Users panel and filter by 'Subscriber' role, or query wp_users table checking wp_capabilities for 'subscriber' valueAffected if Any Subscriber-level user accounts exist in the system
A WordPress site is affected if the Mementor Core plugin version 2.2.5 or lower is installed, the user switch back feature is enabled, and at least one Subscriber-level user account exists that could exploit the missing authorization check.
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 Mementor Core plugin to version 2.2.6 or later, which contains proper access control checks on the user switch back functionality. Until patched, consider disabling the user switching functionality or restricting plugin access.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11168 — 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-11168 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