CVE-2025-56008
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 · uneditedCross site scripting (XSS) vulnerability in KeeneticOS before 4.3 at "Wireless ISP" page allows attackers located near to the router to takeover the device via adding additional users with full permissions.
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 confidenceStored XSS vulnerability in the Wireless ISP configuration page of KeeneticOS versions prior to 4.3 allows attackers with local network proximity to inject malicious scripts. Successful exploitation enables adding new administrative users with full permissions, resulting in complete device takeover.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 4.3CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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.
-
Determine KeeneticOS firmware versionAccess the web interface, navigate to System > About, or use CLI command 'show version' to identify the installed firmware versionAffected if Version is below 4.3 (e.g., 4.2.x, 4.1.x, etc.)
-
Verify Wireless ISP feature statusIn the web interface, navigate to Wireless > ISP or Wireless > WISP to check if this feature is configured or enabledAffected if Wireless ISP is enabled and configured with user-supplied values
-
Confirm administrative access existsLog into the Keenetic web interface and navigate to Users > Administration to check for any unauthorized admin accountsAffected if New or unknown administrative users with full permissions are present
If the installed KeeneticOS version is below 4.3 AND the Wireless ISP feature is enabled, the environment is vulnerable to this stored XSS leading to device compromise.
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 · scoped4.3
Upgrade KeeneticOS to version 4.3 or later to remediate this vulnerability; this firmware update addresses the XSS flaw in the Wireless ISP page.
KeeneticOS 4.3
- Log into the Keenetic router web interface
- Navigate to the System settings or Administration section
- Locate the Firmware Update or Internet Center > Firmware section
- Check the current firmware version (should be below 4.3)
- Initiate firmware update to version 4.3 or later
- Allow the upgrade process to complete and wait for the router to reboot
- Verify the new firmware version is 4.3 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-56008 — 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-56008 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