# CVE-2025-32367: Missing authorization in face recognition application

> Attackers can retrieve personally identifiable information via insecure direct object reference in the statistics endpoint.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Apr 2025
- **Updated:** 11 Apr 2025
- **Also known as:** GHSA-wv3j-j89q-mvh8

## What is CVE-2025-32367?

CVE-2025-32367 is a high-severity missing authorization vulnerability in Oz Forensics face recognition application, published on 11 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Oz Forensics face recognition application before 4.0.8 late 2023 allows PII retrieval via /statistic/list Insecure Direct Object Reference. NOTE: the number 4.0.8 was used for both the unpatched and patched versions.

Weakness: CWE-425 (Direct Request)

## Which versions are affected by CVE-2025-32367?


## How do I fix CVE-2025-32367?

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

## Is CVE-2025-32367 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-32367 and fix it if it is affected.

What it is: CVE-2025-32367 is a high-severity missing authorization vulnerability in Oz Forensics face recognition application, published on 11 Apr 2025. 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-2025-32367 exists.

Affected product: Oz Forensics face recognition application. 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-2025-32367/ (Markdown: https://insights.sbomify.com/CVE-2025-32367/index.md)
```

## Sources

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

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