Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-2418: CWE-287 Improper Authentication in Login with Salesforce

0
Critical
VulnerabilityCVE-2026-2418cvecve-2026-2418cwe-287
Published: Thu Mar 05 2026 (03/05/2026, 06:00:03 UTC)
Source: CVE Database V5
Product: Login with Salesforce

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

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/03/2026, 03:35:01 UTC

Technical Analysis

CVE-2026-2418 is an improper authentication vulnerability classified under CWE-287 affecting the Login with Salesforce WordPress plugin versions through 1.0.2. The vulnerability stems from the plugin's failure to validate that users attempting to authenticate via Salesforce are authorized to do so. Specifically, the plugin allows an attacker who knows a valid user's email address to bypass authentication controls and log in as that user without any credentials or interaction. This means an attacker can impersonate any user, including administrators, simply by supplying their email address during the login process. The vulnerability is remotely exploitable over the network without requiring any privileges or user interaction, making it highly accessible to attackers. The CVSS v3.1 base score is 9.1 (critical), reflecting the ease of exploitation and the high impact on confidentiality and integrity, although availability is not affected. The vulnerability compromises the authentication mechanism, a fundamental security control, thereby undermining the entire security posture of affected WordPress sites using this plugin. No patches or fixes are currently linked, and no known exploits have been reported in the wild as of the publication date. However, the severity and simplicity of exploitation make this a critical threat that demands immediate attention from site administrators and security teams.

Potential Impact

The impact of CVE-2026-2418 is severe for organizations using the Login with Salesforce WordPress plugin. Successful exploitation allows attackers to impersonate any user, including administrators, leading to full account takeover. This can result in unauthorized access to sensitive business data, modification or deletion of content, and potential deployment of further malicious activities such as malware installation or data exfiltration. The breach of administrative accounts can compromise the entire WordPress site, affecting availability indirectly through sabotage or defacement. Organizations relying on Salesforce integration for authentication are particularly vulnerable, risking exposure of confidential customer and corporate data. The vulnerability's network accessibility and lack of required authentication or user interaction make it easy to exploit at scale, increasing the risk of widespread attacks. This can damage organizational reputation, cause regulatory compliance violations, and incur financial losses due to data breaches and remediation costs.

Mitigation Recommendations

1. Immediately disable the Login with Salesforce plugin until a secure patched version is released. 2. Monitor and audit WordPress user login logs for suspicious activity, especially logins from unknown IP addresses or unusual times. 3. Implement multi-factor authentication (MFA) on WordPress accounts to add an additional layer of security beyond the vulnerable plugin. 4. Restrict access to WordPress admin interfaces by IP whitelisting or VPN to reduce exposure. 5. If possible, replace the plugin with alternative, well-maintained Salesforce authentication solutions that properly validate user authorization. 6. Conduct a thorough review of user accounts and permissions to identify and remediate any unauthorized access. 7. Keep WordPress core and all plugins updated regularly to minimize exposure to known vulnerabilities. 8. Employ web application firewalls (WAFs) with rules to detect and block suspicious login attempts targeting this vulnerability. 9. Educate administrators and users about the risk and encourage immediate reporting of any anomalies. 10. Prepare an incident response plan to quickly contain and remediate any exploitation attempts.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
WPScan
Date Reserved
2026-02-12T18:55:02.208Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69a9206cd1a09e29cbe6d01e

Added to database: 3/5/2026, 6:19:24 AM

Last enriched: 4/3/2026, 3:35:01 AM

Last updated: 4/19/2026, 10:55:18 AM

Views: 112

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses