CVE-2025-28170: Grandstream Networks GXP1628 <=1.0.4.130 is vulnerable to Incorrect Access Control
CVE-2025-28170 is a high-severity flaw (CVSS 7.6) affecting gxp1628 firmware. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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.
Why this priority
- High severity
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.6 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | Low |
| User interaction | None |
| EPSS exploit chance | 0.3% (top 74%) |
| CISA exploited list | No |
| Weakness | CWE-548 |
| Published | 2025-07-29 |
| Last modified | 2026-07-05 |
Last updated 2026-07-05 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2025-28170?
gxp1628 firmware: upgrade to newer than 1.0.4.130. Exact commands for each OS are on this page.
Is CVE-2025-28170 being exploited?
CVE-2025-28170 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2025-28170 affect?
CVE-2025-28170 affects gxp1628 firmware. Severity is high (CVSS 7.6). 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.
How urgent is CVE-2025-28170?
Priority 38/100. High severity; Public exploit reference
Related CVEs
- CVE-2026-2329 CRITICAL 9.8 UPGRADE UPGRADE An unauthenticated stack-based buffer overflow vulnerability exists in the HTTP API endpoint /cgi-bin/api.valu