CVE-2026-22337
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 · uneditedIncorrect Privilege Assignment vulnerability in Directorist Directorist Social Login allows Privilege Escalation.This issue affects Directorist Social Login: from n/a before 2.1.4.
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 confidenceThis is an Incorrect Privilege Assignment vulnerability in the Directorist Social Login WordPress plugin that allows attackers to escalate their privileges, likely gaining administrative access. The critical CVSS 9.8 score indicates this can be exploited by unauthenticated attackers.
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.
-
Verify Directorist Social Login plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'Directorist Social Login' in the list of active or inactive plugins.Affected if The plugin is present in the WordPress installation (either active or inactive).
-
Check installed plugin versionIn the Plugins list, locate Directorist Social Login and view the version number displayed beneath the plugin name. Alternatively, open the main plugin file (e.g., directorist-social-login.php) and check the 'Version:' header comment.Affected if The installed version is any version prior to 2.1.4 (e.g., 2.1.3, 2.1.2, older).
-
Review user accounts for unauthorized administratorsGo to WordPress admin > Users. Examine the list of users with 'Administrator' role. Check for unfamiliar admin accounts, accounts with suspicious usernames, or accounts created recently that you did not create.Affected if There are admin-level accounts that were not created by legitimate administrators, or unexpected accounts exist.
-
Inspect social login configuration settingsNavigate to Settings > Social Login (or Directorist > Social Login) in the WordPress admin. Review which social login providers are enabled and examine the role assignment settings for new users registering via social login.Affected if Social login is enabled and configured to assign elevated privileges to newly registered users.
A user is affected if the Directorist Social Login plugin version is below 2.1.4 and the plugin is installed, particularly if social login functionality is enabled.
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 · scopedUpdate Directorist Social Login plugin to version 2.1.4 or later to patch the privilege escalation vulnerability. Audit user accounts for unauthorized administrative access.
2.1.4
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate the Directorist Social Login plugin
- 4. If an update is available, click 'Update Now' to update to the latest version
- 5. Verify the plugin has been updated to version 2.1.4 or later
- 6. Test the social login functionality to ensure it works correctly after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22337 — 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-2026-22337 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