# CVE-2026-2418: Login with Salesforce <= 1.0.2 - Unauthenticated Authentication Bypass

> Unauthenticated attackers can log in as any user, including admins, by knowing their email address due to missing validation in the Login with Salesforce plugin.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Mar 2026
- **Updated:** 2 Apr 2026
- **Also known as:** GHSA-22f9-qcfx-q3w3

## What is CVE-2026-2418?

CVE-2026-2418 is a critical authentication bypass vulnerability in Unknown Login with Salesforce, published on 5 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The 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

## Which versions are affected by CVE-2026-2418?


## How do I fix CVE-2026-2418?

No fix has been published for CVE-2026-2418 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-2418 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2418 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-2418 and fix it if it is affected.

What it is: CVE-2026-2418 is a critical authentication bypass vulnerability in Unknown Login with Salesforce, published on 5 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2418 exists.

Affected product: Unknown Login with Salesforce. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-2418/ (Markdown: https://insights.sbomify.com/CVE-2026-2418/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-2418
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2418
- OSV: https://osv.dev/vulnerability/CVE-2026-2418

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-2418/
Summaries are generated and may contain mistakes; the official description above is the record.