CVE-2025-65007
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 · uneditedIn WODESYS WD-R608U router (also known as WDR122B V2.0 and WDR28) due to lack of authentication in the configuration change module in the adm.cgi endpoint, the unauthenticated attacker can execute commands including backup creation, device restart and resetting the device to factory settings. The vendor was notified early about this vulnerability, but didn't respond with the details of vulnerability or vulnerable version range. Only version WDR28081123OV1.01 was tested and confirmed as vulnerable, other versions were not tested and might also be vulnerable.
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 · high confidenceThe WODESYS WD-R608U router (models WDR122B V2.0 and WDR28) contains an authentication bypass vulnerability in the adm.cgi endpoint's configuration change module. An unauthenticated attacker can execute arbitrary commands including creating device backups, restarting the router, and resetting to factory settings due to the complete absence of authentication checks.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 device modelCheck the router's web interface status page, device label, or boot logs for the model number. Look for WODESYS WD-R608U, WDR122B V2.0, or WDR28.Affected if The device is a WODESYS WD-R608U router (models WDR122B V2.0 or WDR28)
-
Verify adm.cgi endpoint existsAccess the router's web interface and navigate to adm.cgi, or attempt a GET request to http://[router-ip]/cgi-bin/adm.cgiAffected if The adm.cgi endpoint is present and responds to requests
-
Test authentication requirement on configuration functionsAttempt to access configuration change functions via adm.cgi without providing any login credentials. This includes triggering actions like backup creation, router restart, or factory reset through direct HTTP requests to the endpoint.Affected if Configuration and management functions in adm.cgi execute without requiring any authentication credentials
-
Check network exposure of management interfaceDetermine if the router's web management interface (port 80/443) is directly accessible from untrusted networks such as the internet, rather than only from a trusted internal network.Affected if The router's management interface is exposed to untrusted networks without firewall protection
You are affected if you operate a WODESYS WD-R608U router (WDR122B V2.0 or WDR28) where the adm.cgi endpoint allows unauthenticated access to configuration change functions.
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 dataSince no vendor patch is available, implement compensating controls such as restricting network access to the device's management interface via firewall rules or network segmentation. If the device is no longer supported, consider replacement with a currently maintained product.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.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,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-65007 — 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-65007 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