Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-77000 – Authentication Bypass (Full Account Takeover) – WP Social Media Login WordPress Plu

Be the first to know when new zero-days emerge:

Summary

CVE-2026-77000 is a critical improper authentication vulnerability (CWE-287) affecting the WP Social Media Login WordPress plugin, versions up to and including 1.0.6. The plugin fails to verify that a social login flow was actually completed with the external identity provider (e.g., Facebook, Google) before establishing an authenticated session, allowing an unauthenticated remote attacker to log in as any existing user — including administrators — by simply supplying that user’s email address. The flaw carries a CVSS v3.1 base score of 9.8 (Critical) and requires no authentication or user interaction to exploit.

Technical details

  • Root cause: The plugin’s social login handler completes the authentication process (issuing a logged-in session) based on user-supplied data without cryptographically or otherwise verifying that the identity provider (social network) actually confirmed the user’s identity.
  • Trigger conditions: An attacker only needs to know or guess the email address of a target WordPress user (site administrators’ emails are often discoverable via author archives, WHOIS, or OSINT).
  • Attack vector: Network-based, unauthenticated, no user interaction required — the attacker directly invokes the plugin’s login endpoint/flow with the victim’s email address instead of completing a legitimate social provider handshake.
  • Impact: Full authentication bypass resulting in complete account takeover, including of administrator accounts. This can lead to full compromise of the WordPress site — arbitrary content changes, installation of malicious plugins/themes, and potential remote code execution via the WordPress admin panel.

Affected software

  • Product: WP Social Media Login (WordPress plugin)
  • Affected versions: All versions through 1.0.6 (0 – 1.0.6 inclusive)

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: No patched version has been publicly documented as of this writing. Security teams should check the WordPress.org plugin repository for an update beyond version 1.0.6 and apply it as soon as it becomes available.
  • If no patch is available:
    • Deactivate and remove the WP Social Media Login plugin from all WordPress installations until a fix is released.
    • Enforce multi-factor authentication for all privileged (administrator/editor) accounts to reduce the impact of any single-factor authentication bypass.
    • Monitor authentication logs for anomalous logins, particularly logins to administrator accounts that do not correspond to a legitimate social-provider redirect/callback.
    • Restrict or monitor access to the plugin’s login/callback endpoints via a web application firewall (WAF) as a compensating control.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge