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

> Attackers can access sensitive files via directory listing if enabled, exposing confidential data on Grandstream GXP1628 devices.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L`)
- **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:** 29 Jul 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-7wqx-pvjm-73q6

## What is CVE-2025-28170?

CVE-2025-28170 is a high-severity vulnerability in n/a, published on 29 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Grandstream Networks GXP1628 <=1.0.4.130 is vulnerable to Incorrect Access Control. The device is configured with directory listing enabled, allowing unauthorized access to sensitive directories and files.

Weakness: CWE-548 (Exposure of Information Through Directory Listing)

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

It affects 1 product.


Products: Grandstream Gxp1628 Firmware.

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

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

## Is CVE-2025-28170 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-28170 is a high-severity vulnerability in n/a, published on 29 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-28170 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-28170/ (Markdown: https://insights.sbomify.com/CVE-2025-28170/index.md)
```

## Sources

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

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