CVE-2025-7072
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 · uneditedThe firmware in KAON CG3000TC and CG3000T routers contains hard-coded credentials in clear text (shared across all routers of this model) that an unauthenticated remote attacker could use to execute commands with root privileges. This vulnerability has been fixed in firmware version: 1.00.67 for CG3000TC and 1.00.27 for CG3000T.
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 KAON CG3000TC and CG3000T routers contain hard-coded credentials stored in clear text within the firmware. These credentials are identical across all units of these models, allowing any unauthenticated remote attacker to gain root-level command execution access to the affected devices.
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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/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 the router modelLocate the model number on the device physical label or check the web admin interface (typically at 192.168.0.1) for the device model informationAffected if Model is CG3000TC or CG3000T
-
Determine the installed firmware versionAccess the router web admin interface and navigate to the firmware or status page to view the current firmware version, or log into the device via telnet/SSH and run the command to display firmware versionAffected if Cannot determine firmware version or version is readable
-
Compare version against fixed releasesFor CG3000TC: verify if version is below 1.00.67. For CG3000T: verify if version is below 1.00.27Affected if CG3000TC firmware is version 1.00.66 or lower, OR CG3000T firmware is version 1.00.26 or lower
The device is affected if it is a CG3000TC running firmware below 1.00.67 or a CG3000T running firmware below 1.00.27, as these versions contain the hard-coded credentials.
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.
dbcve · scopedUpgrade router firmware to version 1.00.67 for CG3000TC or 1.00.27 for CG3000T to replace the vulnerable firmware containing the hard-coded credentials.
Firmware 1.00.67 for CG3000TC or 1.00.27 for CG3000T
- 1. Identify the exact KAON router model (CG3000TC or CG3000T)
- 2. Check the current firmware version through the router's web interface or administration panel
- 3. Download firmware version 1.00.67 for CG3000TC or version 1.00.27 for CG3000T from the official KAON vendor website or trusted source
- 4. Access the router's administration panel and navigate to the firmware upgrade section
- 5. Upload the appropriate firmware file and initiate the upgrade
- 6. Allow the router to complete the firmware update and reboot automatically
- 7. After reboot, verify the new firmware version is installed and confirm the hard-coded credentials have been removed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7072 — 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-7072 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