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

> Unauthenticated attackers can read confidential documents via an IDOR vulnerability in the PdfHandler component of Eccobook.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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:** 5 Aug 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-97f9-42cr-fpvx

## What is CVE-2025-51628?

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

### Official description

Insecure Direct Object Reference (IDOR) vulnerability in PdfHandler component in Agenzia Impresa Eccobook v2.81.1 and below allows unauthenticated attackers to read confidential documents via the DocumentoId parameter.

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

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


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

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

## Is CVE-2025-51628 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-51628 is a high-severity vulnerability in n/a, published on 5 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-51628 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-51628/ (Markdown: https://insights.sbomify.com/CVE-2025-51628/index.md)
```

## Sources

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

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