# CVE-2026-93984: OpenPanel API through 2.3.0 Authentication Bypass via Unverified Client Secret

> Attackers can bypass authentication to inject forged revenue metrics and evade bot detection in OpenPanel tracking API.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Sep 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-2m8f-94rg-j65x, GHSA-956w-65qh-w3jh

## What is CVE-2026-93984?

CVE-2026-93984 is a medium-severity authentication bypass vulnerability in Openpanel-dev openpanel, published on 19 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenPanel tracking API through 2.3.0 fails to verify client secret cryptographic hash before authorizing revenue events and bot filtering. Attackers with only a public client ID can supply arbitrary dummy secrets to inject forged revenue metrics and bypass bot detection filters.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-93984 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-93984 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93984 is a medium-severity authentication bypass vulnerability in Openpanel-dev openpanel, published on 19 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-93984 exists.

Affected product: Openpanel-dev openpanel. 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-93984/ (Markdown: https://insights.sbomify.com/CVE-2026-93984/index.md)
```

## Sources

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

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