CVE-2026-8787
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Firebase Support & Chat Management plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 3.1.1. This is due to the `firebase_auth()` function authenticating the request as the WordPress user whose email is supplied in the `user_email` POST parameter without verifying ownership of that email (no Firebase ID token signature/issuer/audience verification). This makes it possible for authenticated attackers, with Subscriber-level access and above, to log in as an arbitrary existing user — including an Administrator — by submitting that user's email address to the `acb_firebase_auth` AJAX action, resulting in full account takeover.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe plugin's `firebase_auth()` function authenticates users based solely on the email address supplied in the `user_email` POST parameter without verifying email ownership or validating Firebase ID token signatures, issuers, or audiences. Attackers with Subscriber-level WordPress access can exploit the `acb_firebase_auth` AJAX action to impersonate any user, including Administrators, achieving full account takeover.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Firebase Support & Chat Management plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Firebase Support & Chat Management' or check the file system for /wp-content/plugins/ folder containing 'firebase' in the directory nameAffected if The plugin is installed and active
-
Determine the installed plugin versionCheck the plugin header in its main PHP file (usually in /wp-content/plugins/[plugin-folder]/ or look at the version in the plugin's readme.txt)Affected if Version is unknown or falls within an unpatched range (the vulnerability exists when proper Firebase ID token validation is not implemented)
-
Confirm the acb_firebase_auth AJAX action is exposedMake a GET or POST request to /wp-admin/admin-ajax.php?action=acb_firebase_auth and verify the endpoint responds (does not return 404 or forbidden)Affected if The AJAX endpoint returns a valid response indicating the vulnerable action is registered and accessible
-
Check if the plugin authentication feature is enabledReview the plugin settings in WordPress admin under the plugin's configuration page for any authentication-related optionsAffected if Firebase authentication or the user authentication feature is enabled in plugin settings
-
Identify user roles with access to the siteIn WordPress admin, go to Users and review which roles exist. Note that Subscriber-level accounts or any authenticated user can trigger the vulnerable AJAX actionAffected if Any user account (Subscriber role or above) exists on the site, allowing them to exploit the flaw
If the Firebase Support & Chat Management plugin is installed with its authentication feature enabled and the acb_firebase_auth AJAX endpoint is accessible to authenticated users, then the environment is vulnerable to account takeover via email impersonation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to a patched version of the Firebase Support & Chat Management plugin that implements proper Firebase ID token validation (signature, issuer, audience verification) before trusting the supplied email address.
Version 3.1.2 or later (verify exact version number at wordpress.org/plugins/firebase-support-chat-management/)
- 1. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins
- 2. Locate the 'Firebase Support & Chat Management' plugin
- 3. Check the current installed version in the plugin details
- 4. Visit the plugin's page at wordpress.org/plugins/firebase-support-chat-management/ or the vendor's site to verify if version 3.1.2 or later is available
- 5. If version 3.1.2 or higher is available, update the plugin directly from the WordPress plugins page
- 6. Alternatively, download the updated version from the WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin
- 7. After updating, verify the fix by confirming the plugin version shows 3.1.2 or later
- 8. Test that the privilege escalation vulnerability is patched by attempting (in a staging environment) to use the acb_firebase_auth AJAX action with another user's email - it should fail or require proper authentication
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,536.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8787 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-8787 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data