# CVE-2026-111708: WhaTicket Community through commit cf04795 Admin Self-Registration via /auth/signup

> Unauthenticated attackers can self-register as administrators via the signup endpoint, gaining full control over user management, settings, and ticket data.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-6xw5-h4c8-ww5j

## What is CVE-2026-111708?

CVE-2026-111708 is a critical authentication bypass vulnerability in canove whaticket-community, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WhaTicket Community through commit cf04795 contains an authentication bypass vulnerability that allows unauthenticated attackers to self-register as administrators via POST /auth/signup. Attackers can omit the profile field or set it to admin, gaining user management, settings, and access to all tickets, contacts, messages, and WhatsApp connections.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-111708 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111708 is a critical authentication bypass vulnerability in canove whaticket-community, published on 16 Oct 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-111708 exists.

Affected product: canove whaticket-community. 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-111708/ (Markdown: https://insights.sbomify.com/CVE-2026-111708/index.md)
```

## Sources

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

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