# CVE-2024-37768: Missing authorization in n/a

> Attackers can arbitrarily delete users via the admin API endpoint due to missing authorization checks in 14Finger.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jul 2024
- **Updated:** 13 Mar 2025
- **Also known as:** GHSA-f33q-f757-3cjh

## What is CVE-2024-37768?

CVE-2024-37768 is a critical missing authorization vulnerability in n/a, published on 5 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

14Finger v1.1 was discovered to contain an arbitrary user deletion vulnerability via the component /api/admin/user?id.

## Which versions are affected by CVE-2024-37768?

It affects 1 product.


Products: B1ackc4t 14finger.

## How do I fix CVE-2024-37768?

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

## Is CVE-2024-37768 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-37770](https://insights.sbomify.com/CVE-2024-37770/): Command injection in n/a (critical 9.1)
- [CVE-2024-37769](https://insights.sbomify.com/CVE-2024-37769/): Privilege escalation in n/a (high 8.8)
- [CVE-2024-37767](https://insights.sbomify.com/CVE-2024-37767/): Missing authorization in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-37768 and fix it if it is affected.

What it is: CVE-2024-37768 is a critical missing authorization vulnerability in n/a, published on 5 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-37768 in the wild and no public exploit code.

Affected product: n/a. 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-2024-37768/ (Markdown: https://insights.sbomify.com/CVE-2024-37768/index.md)
```

## Sources

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

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