CVE-2025-29524
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIncorrect access control in the component /cgi-bin/system_diagnostic_main.asp of DASAN GPON ONU H660WM H660WMR210825 allows attackers to access sensitive information.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe vulnerability exists in the CGI script /cgi-bin/system_diagnostic_main.asp on DASAN GPON ONU H660WM and H660WMR210825 devices. Due to incorrect access control implementation, unauthenticated attackers can access this diagnostic page and retrieve sensitive system information without proper authorization.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the device web interface or check the device label/sticker for the model number. Look for 'H660WM' or 'H660WMR210825' markings indicating DASAN GPON ONU hardware.Affected if The device is a DASAN GPON ONU H660WM or H660WMR210825 model.
-
Verify the CGI script existsSend an HTTP GET request to http://<device_ip>/cgi-bin/system_diagnostic_main.asp without providing any authentication credentials. Check if the server responds with HTTP 200 and returns diagnostic content.Affected if The endpoint returns diagnostic or system information without requiring login credentials.
-
Confirm the page contains sensitive dataExamine the response from the /cgi-bin/system_diagnostic_main.asp endpoint. Look for system configuration, firmware version, network settings, or other sensitive information that should require authentication.Affected if The page displays system details such as firmware version, network configuration, device status, or other sensitive parameters without being logged in.
-
Check if default credentials are not requiredAttempt to access the diagnostic page after deliberately failing or omitting login credentials. Verify that no authentication challenge (HTTP 401, redirect to login page, or session check) blocks the request.Affected if The diagnostic page is accessible without any valid session token or login credentials.
A user is affected if they operate a DASAN H660WM or H660WMR210825 device where the /cgi-bin/system_diagnostic_main.asp endpoint returns sensitive system information to unauthenticated requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor firmware patch when available; until then, restrict network access to the device management interface using firewall rules or VLAN segmentation to prevent unauthorized access to the /cgi-bin/ endpoints.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,872.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-29524 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-29524 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data