CyberSecBulletin
CVE-2025-32367NVD status: Deferred

face recognition application: Direct Request

CVE-2025-32367 is a high-severity direct request vulnerability in face recognition application from Oz Forensics, with a CVSS 3.1 base score of 8.6 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 4.0.8 late 2023 as the first without the flaw, so updating face recognition application to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.45% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update face recognition application to 4.0.8 late 2023 or a later version.
  2. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
Oz Forensicsface recognition applicationbefore 4.0.8 late 20234.0.8 late 2023

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
ChangedThe attack can reach beyond the vulnerable component into other systems.
Confidentiality
HighAll data handled by the component can be read.
Integrity
NoneNothing can be modified.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N. Scored by CNA (mitre.org).

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Direct Request

The web application does not adequately enforce appropriate authorization on all restricted URLs, scripts, or files.

How developers prevent this class of flaw

  • Apply appropriate access control authorizations for each access to all restricted URLs, scripts or files.
  • Consider using MVC based frameworks such as Struts.

More Direct Request vulnerabilities (CWE-425)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Direct Request vulnerabilities

Spotted an error? Tell us.