# CVE-2025-45968: Information disclosure in n/a

> Remote attackers can access sensitive data via IDOR in System PDV due to missing authorization checks on the hash parameter.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 25 Aug 2025
- **Updated:** 25 Aug 2025
- **Also known as:** GHSA-2xjf-r5x5-5xpc

## What is CVE-2025-45968?

CVE-2025-45968 is a critical vulnerability in n/a, published on 25 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in System PDV v1.0 allows a remote attacker to obtain sensitive information via the hash parameter in a URL. The application contains an Insecure Direct Object Reference (IDOR) vulnerability, which occurs due to a lack of proper authorization checks when accessing objects referenced by this parameter. This allows direct access to other users' data or internal resources without proper permission. Successful exploitation of this flaw may result in the exposure of sensitive information.

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

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

It affects 1 product.


Products: System Pdv Project System Pdv.

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

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

## Is CVE-2025-45968 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-45968 is a critical vulnerability in n/a, published on 25 Aug 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-45968 exists.

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-2025-45968/ (Markdown: https://insights.sbomify.com/CVE-2025-45968/index.md)
```

## Sources

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

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