CVE-2026-2418
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 Login with Salesforce WordPress plugin through 1.0.2 does not validate that users are allowed to login through Salesforce, allowing unauthenticated users to be authenticated as any user (such as admin) by simply knowing the 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 Login with Salesforce WordPress plugin through version 1.0.2 lacks proper authorization validation during the Salesforce OAuth login process. An attacker can authenticate via Salesforce using any email address and gain access to the corresponding WordPress user account (including administrator accounts) without the user being authorized for Salesforce login.
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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
-
Verify the Login with Salesforce plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Login with Salesforce' or check the wp-content/plugins directory for a salesforce-related folderAffected if The plugin is present on the WordPress site
-
Determine the installed plugin versionCheck the plugin header in the main plugin PHP file (typically wp-content/plugins/login-with-salesforce/login-with-salesforce.php or similar) for the 'Version' comment, or view the plugin details in the WordPress Plugins admin pageAffected if The version is 1.0.2 or lower
-
Confirm Salesforce SSO login functionality is enabledCheck WordPress options table (wp_options) for salesforce-related settings, or look in the plugin settings page under Users > Salesforce Login or similar admin menu item to see if the feature is activeAffected if Salesforce SSO login is enabled and accessible to users
-
Verify the vulnerable authentication endpoint is accessibleAttempt to access the plugin login endpoint (commonly /wp-login.php?oauth1=salesforce or similar Salesforce auth route) without authentication and observe if it accepts an arbitrary email parameterAffected if The endpoint accepts unauthenticated requests with arbitrary email addresses for authentication
The environment is affected if the Login with Salesforce plugin version 1.0.2 or lower is installed with Salesforce SSO login enabled, allowing unauthenticated attackers to impersonate any user by providing their email address.
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 to the latest patched version of the plugin that implements proper validation ensuring only authorized users can authenticate via Salesforce, or restrict the plugin's login capability to a vetted user whitelist.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2418 — 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-2418 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