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

Back
New CVE Detected

CVE-2026-76793 – Unauthenticated Account Takeover – Firebase Authentication WordPress Plugin < 1.7.1

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-76793 is an authentication bypass vulnerability affecting the Firebase Authentication plugin for WordPress. Versions prior to 1.7.1 fail to verify that the email address embedded in a Firebase authentication token has actually been confirmed as verified before using it to match and log into a corresponding WordPress account. This flaw is rated HIGH severity (CVSS 3.1: 8.1) and allows an unauthenticated attacker to take over any WordPress account tied to a matching email, including administrator accounts.

Technical details

  • Root cause: The plugin trusts the email claim inside a Firebase-issued authentication token to identify and log a user into WordPress, without first confirming that the email address associated with that token has been verified by Firebase.
  • Trigger conditions: An attacker who can obtain or craft a Firebase authentication token containing an unverified email address matching a target WordPress account’s email can present it to the plugin’s login handler.
  • Attack vector: Network-based (AV:N); the CVSS vector reflects high attack complexity (AC:H) and requires no privileges (PR:N) or user interaction (UI:N), meaning no valid credentials or victim action are needed for exploitation.
  • Impact: Successful exploitation results in full impersonation of the targeted WordPress account, including potential administrator takeover, with high impact to confidentiality, integrity, and availability (C:H/I:H/A:H) — potentially leading to complete site compromise.
  • Classification: CWE-287 (Improper Authentication).

Affected software

  • Firebase Authentication WordPress plugin — all versions prior to 1.7.1

Severity

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

Mitigation and recommended actions

  • Immediate: Upgrade the Firebase Authentication WordPress plugin to version 1.7.1 or later, which enforces proper verification of the email claim in Firebase authentication tokens before account linking/login.
  • If immediate patching is not possible:
    • Temporarily disable the Firebase Authentication plugin to prevent token-based logins until the patch can be applied.
    • Review WordPress user accounts and audit logs for suspicious logins or unexpected administrative activity that may indicate prior exploitation.
    • Enforce additional authentication controls (e.g., two-factor authentication for administrator accounts) as a compensating control while patching is scheduled.
    • Restrict or monitor exposure of the plugin’s authentication endpoints where feasible until the update is deployed.

References

Are you exposed?

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge