# CVE-2026-8787: Firebase Support & Chat Management <= 3.1.1 - Missing Authorization to Authenticated (Subscriber+) Privilege Escalation

> Authenticated subscribers can escalate privileges to administrator by spoofing email addresses in the Firebase authentication function.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 May 2026
- **Updated:** 27 May 2026
- **Also known as:** GHSA-g86w-5353-83r2

## What is CVE-2026-8787?

CVE-2026-8787 is a high-severity authentication bypass vulnerability in devsabbirahmed Firebase Support & Chat Management, published on 27 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The 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.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2026-8787?


## How do I fix CVE-2026-8787?

No fix has been published for CVE-2026-8787 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-8787 being exploited?

There is no known exploitation of CVE-2026-8787 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8787 and fix it if it is affected.

What it is: CVE-2026-8787 is a high-severity authentication bypass vulnerability in devsabbirahmed Firebase Support & Chat Management, published on 27 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-8787 in the wild and no public exploit code.

Affected product: devsabbirahmed Firebase Support & Chat Management. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-8787/ (Markdown: https://insights.sbomify.com/CVE-2026-8787/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-8787
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-8787
- OSV: https://osv.dev/vulnerability/CVE-2026-8787

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-8787/
Summaries are generated and may contain mistakes; the official description above is the record.