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

> Unauthenticated attackers can access diagnostic endpoints in Sage DPW to expose sensitive data like hashes and table names if the feature is enabled.

- **Severity:** Medium 5.9 (`CVSS:3.1/AC:H/AV:N/A:N/C:H/I:N/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Apr 2026
- **Updated:** 10 May 2026
- **Also known as:** GHSA-9wf6-7mhp-pg5q

## What is CVE-2025-67805?

CVE-2025-67805 is a medium-severity vulnerability in n/a, published on 1 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A non-default configuration in Sage DPW 2025_06_004 allows unauthenticated access to diagnostic endpoints within the Database Monitor feature, exposing sensitive information such as hashes and table names. This feature is disabled by default in all installations and never available in Sage DPW Cloud. It was forcibly disabled again in version 2025_06_003.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Sagedpw Sage Dpw.

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

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

## Is CVE-2025-67805 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-56883](https://insights.sbomify.com/CVE-2024-56883/): Missing authorization in n/a (high 8.1)
- [CVE-2025-51532](https://insights.sbomify.com/CVE-2025-51532/): Missing authorization in n/a (high 7.5)
- [CVE-2025-51531](https://insights.sbomify.com/CVE-2025-51531/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2020-26583](https://insights.sbomify.com/CVE-2020-26583/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2020-26584](https://insights.sbomify.com/CVE-2020-26584/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-67805 is a medium-severity vulnerability in n/a, published on 1 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-67805 in the wild and no public exploit code.

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

## Sources

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

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