# CVE-2025-7347: IDOR in Dinibh Puzzle's Dinibh Patrol Tracking System

> Attackers can bypass authorization to access or modify patrol tracking data by manipulating user-controlled identifiers in the Dinibh Patrol Tracking System.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Feb 2026
- **Updated:** 5 Jun 2026
- **Also known as:** GHSA-jgg6-7gq8-598m

## What is CVE-2025-7347?

CVE-2025-7347 is a high-severity missing authorization vulnerability in Dinibh Patrol Tracking System, published on 10 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Authorization Bypass Through User-Controlled Key vulnerability in Dinibh Puzzle Software Solutions Dinibh Patrol Tracking System allows Exploitation of Trusted Identifiers.

This issue affects Dinibh Patrol Tracking System: through 10022026.

NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2025-7347 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7347 is a high-severity missing authorization vulnerability in Dinibh Patrol Tracking System, published on 10 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-7347 in the wild and no public exploit code.

Affected product: Dinibh Patrol Tracking System. 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-7347/ (Markdown: https://insights.sbomify.com/CVE-2025-7347/index.md)
```

## Sources

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

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