CVE-2026-76793: Firebase Authentication (WordPress plugin) · Improper Authentication
Affects Firebase Authentication (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 8.1 High : upgrade to 1.7.1 soon.
Data as of 20 Nov 2026, 17:35 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.7.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 22 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade Firebase Authentication (WordPress plugin) to 1.7.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Firebase Authentication | Affected
| Fixed in
|
AI-suggested
A patch is available for this vulnerability. Users should upgrade the Firebase Authentication WordPress plugin to version 1.7.1 or later to remediate the issue. Since this is a plugin vulnerability, applying the official update is the recommended and effective mitigation.
Description
CVE-2026-76793 is a high-severity vulnerability in the Firebase Authentication WordPress plugin before version 1.7.1. The flaw allows unauthenticated attackers to log in as any user, including administrators, because the plugin does not verify the email address in an authentication token before matching it to a WordPress account and issuing a session.