DWSurvey v6.14.0 is is vulnerable to authentication bypass via the '/api/dwsurvey/none/' and '/api/dwsurvey/up/**' parameters.
CVE-2026-75325
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-26. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(high)
- EG Risk
- 75(Attend)EG Risk 75/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 27%
- KEV
- Not listed
Published
August 26, 2026
Last Modified
August 27, 2026
Advisory Details (1)
Auto-updated Aug 27, 2026CVE/DWSurvey/DWSurvey 未授权访问漏洞.md at main · fangtang7/CVE · GitHub
https://github.com/fangtang7/CVE/blob/main/DWSurvey/DWSurvey%20%E6%9C%AA%E6%8E%88%E6%9D%83%E8%AE%BF%E9%97%AE%E6%BC%8F%E6%B4%9E.mdVendor Advisories for CVE-2026-75325(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 27× in last 7d / 27× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 05:48 UTCGHSA enrichment
- 2026-08-30 01:40 UTCEG score recompute
- 2026-08-30 01:40 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 21:32 UTCGHSA enrichment
- 2026-08-29 17:25 UTCGHSA enrichment
- 2026-08-29 12:32 UTCGHSA enrichment
- 2026-08-29 08:21 UTCGHSA enrichment
- 2026-08-29 04:09 UTCGHSA enrichment
- 2026-08-28 23:59 UTCEG score recompute
- 2026-08-28 23:59 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 17:20 UTCGHSA enrichment
- 2026-08-28 13:10 UTCGHSA enrichment
- 2026-08-28 09:01 UTCGHSA enrichment
- 2026-08-28 04:52 UTCGHSA enrichment
- 2026-08-28 00:44 UTCEG score recompute
- 2026-08-28 00:44 UTCGHSA enrichment
- 2026-08-27 20:28 UTCEG score recompute
- 2026-08-27 20:28 UTCGHSA enrichment
- 2026-08-27 20:16 UTCEG score recompute▲ 9.80
- 2026-08-27 20:16 UTCGHSA enrichment
- 2026-08-27 20:13 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 19:22 UTCNVD update
Show 2 moreShow fewer
- 2026-08-26 18:41 UTCEG score recompute
- 2026-08-26 18:41 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-287
Frequently asked(5)
What is CVE-2026-75325?
When was CVE-2026-75325 disclosed?
Is CVE-2026-75325 actively exploited?
What is the CVSS score of CVE-2026-75325?
How do I remediate CVE-2026-75325?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-75325
Is Your Infrastructure Affected by CVE-2026-75325?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.